ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn when to expose Ceylon declarations with shared visibility and when to keep them package‑private, with a decision table, trade‑off discussion, and a minimal validation example.
Vyper uses decorators to declare function visibility and payable status. This guide shows how @external, @internal, and @payable work together, with a concrete example, limits, and common mistakes.
Since Solidity 0.5.0, the compiler rejects any function declared without an explicit visibility specifier. Before that release, a missing keyword silently defaulted to public — a classic route to accidental external access. Function visibility is now mandatory, but the neighboring state-variable decision remains open. State variables default to internal, yet
Problem When building a shared library, global symbols that are not intended for external use can be inadvertently exported, leading to namespace pollution or security concerns. The C language provides the static keyword for internal linkage, but the default visibility rules differ across compilers and platforms. Additionally, visibility attributes and linke
Missing Visibility Enforcement for Stereotyped Elements The UML 2.5 specification defines stereotypes as reusable profile extensions but does not prescribe a mandatory visibility constraint for the elements they annotate. This omission leaves tool-specific behavior undefined: a stereotype applied to a class marked private may be rendered public in generated
Gleam 1.x treats every top-level function as private unless it carries the pub keyword. Code written against earlier releases that relied on implicit cross-module access therefore sits on a compatibility boundary: source that compiled before now needs an explicit export decision for each function another module calls. That decision is straightforward for a l
Potentially Visible Set (PVS) and Occluder Depth The Source Engine builds a PVS from the current BSP leaf, using static world brushes and dynamic props flagged as occluder to prune entities each frame. While the engine documentation confirms that occluders block visibility, it does not expose a maximum depth or a hard limit on how many nested occluders the t
Vyper creates an external read-only getter for any state variable declared public and treats functions as external by default. The internal modifier must be added explicitly to keep helper logic from being callable externally. The goal is to understand the documented capability limits around accidental exposure: when a public variable is used unintentionally
Context secrets exposed when project visibility changes to public Problem statement CircleCI contexts allow sharing environment variables across projects, but the documentation does not clearly specify whether secrets stored in contexts remain accessible to users with read-only permissions when a project's visibility changes from private to public. This crea
vyper
solidity
gleam
sourceengine
circleci