ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal: enable fine‑grained control over which Ceylon packages are exported as JPMS modules when the module is consumed from Java 9+ without leaking internal APIs. Constraint: the Ceylon 1.3.4 compiler generates a module‑info.class that exports every package containing a shared declaration, treating internal shared packages as public exports; there is no langu
Goal I want to keep a Jule package's internal types and functions inaccessible to importing packages, exposing only a minimal API surface. My concern is accidental public access: a declaration that I intended to be package-private ending up callable from outside the package. Constraint and uncertainty Jule documents visibility through an explicit access modi
Understanding Nomad Job Publish Stanza and ACL Policy Interaction The publish stanza in a Nomad job definition controls whether the job appears in the UI and API. When ACLs are enabled, token policies can further restrict visibility. The exact precedence between the publish setting and ACL enforcement is not fully documented, especially for jobs that omit th
Designing an F# library with the goal of avoiding accidental public access requires clear understanding of how access modifiers compose for modules and nested types. Top-level modules and types are public by default, so internal is used to restrict them to the assembly. Nested modules and types default to private, visible only within the enclosing module or
jule
fsharp
ceylon