feat(lang): L3 module scope - module, export, friend module
A barrel's 'module NAME' makes its directory a module; a declaration other modules use says 'export'. Private use from another module is an error naming the module and where to mark it; 'friend module' sees everything (a test harness); a file in no module is public and a package keeps its own module. LUDIC_VIS_REPORT=1 lists every violation instead of stopping, so a codebase can be given its exports first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
0c73287e35
commit
0677aee93f
20 changed files with 55913 additions and 54132 deletions
8
changes/module-scope.md
Normal file
8
changes/module-scope.md
Normal file
|
|
@ -0,0 +1,8 @@
|
|||
bump: minor
|
||||
type: feature
|
||||
**Modules.** `module NAME` in a barrel makes its directory a module, and a module's
|
||||
declarations are private to it unless they say `export`: a function, global, record or event of
|
||||
another module used without one is an error naming the module and where to mark it. `friend
|
||||
module NAME` sees everything (a test harness), a file in no module is public, and a package keeps
|
||||
its own module. `LUDIC_VIS_REPORT=1` lists every violation instead of stopping, so an existing
|
||||
program can be given its exports by a script before the rule applies to it.
|
||||
Loading…
Add table
Add a link
Reference in a new issue