implements PR-19.1 normative spec propagation
This commit is contained in:
@@ -40,7 +40,7 @@ Rules:
|
||||
|
||||
- `declare struct`, `declare service`, `declare contract`, `declare error`, `declare enum`, `declare callback`, and `declare builtin type` introduce names in the type namespace.
|
||||
- `declare host` introduces names in the host-owner namespace.
|
||||
- `let`, parameters, and `declare const` introduce names in the value namespace.
|
||||
- `let`, parameters, `declare const`, and `declare global` introduce names in the value namespace.
|
||||
- `declare service Name` also introduces the canonical singleton value `Name` in the value namespace.
|
||||
- Top-level `fn`, service methods, and host methods participate in the callable namespace.
|
||||
- `fn` declarations are not first-class values in v1 core and therefore do not become ordinary value expressions.
|
||||
@@ -62,9 +62,12 @@ Rules:
|
||||
- Attributes are not first-class values and are not reflectable in v1 core.
|
||||
- Attributes do not automatically survive into runtime or bytecode artifacts.
|
||||
- An attribute affects runtime artifacts only when another specification defines an explicit lowering for its semantic effect.
|
||||
- In v1 core, the normative reserved attributes are `Host`, `Capability`, `BuiltinType`, `BuiltinConst`, and `IntrinsicCall`.
|
||||
- In v1 core, the normative reserved attributes are `Host`, `Capability`, `BuiltinType`, `BuiltinConst`, `IntrinsicCall`, `Init`, `Frame`, and `InitAllowed`.
|
||||
- `Host` is valid only on a host method signature declared directly inside a reserved stdlib/interface-module `declare host` body.
|
||||
- `Capability` is valid only on a host method signature declared directly inside a reserved stdlib/interface-module `declare host` body.
|
||||
- `Init` is valid only on a top-level userland `fn` declaration with lifecycle-admissible signature.
|
||||
- `Frame` is valid only on a top-level userland `fn` declaration with lifecycle-admissible signature.
|
||||
- `InitAllowed` is valid only on a host method signature declared directly inside a reserved stdlib/interface-module `declare host` body.
|
||||
- `Host` is invalid on ordinary user-authored modules, top-level `fn`, struct methods, service methods, callbacks, contracts, and constants.
|
||||
- `Host` metadata is consumed by the compiler during host-binding lowering.
|
||||
- The `Host` attribute syntax itself is not exported as runtime metadata; instead, its canonical identity participates in PBX host-binding emission as defined by the Host ABI Binding specification.
|
||||
@@ -72,6 +75,8 @@ Rules:
|
||||
- `BuiltinConst` is valid only on a reserved top-level `declare const` declaration that omits an initializer.
|
||||
- `IntrinsicCall` is valid only on a method signature declared directly inside a reserved `declare builtin type` body.
|
||||
- Builtin metadata is consumed by the compiler during VM-owned builtin and intrinsic lowering rather than by host-binding lowering.
|
||||
- `Init` and `Frame` are consumed by lifecycle analysis and lowering rather than by ordinary runtime reflection.
|
||||
- `InitAllowed` is consumed by init-time host-admission analysis and does not become ordinary userland metadata.
|
||||
|
||||
### 2.4 Tuple shapes
|
||||
|
||||
@@ -168,6 +173,20 @@ Rules:
|
||||
- Any return surface that combines `optional` and `result` is statically invalid.
|
||||
- Any payload-less `optional` type surface is statically invalid.
|
||||
- Any `optional void` type surface is statically invalid.
|
||||
- A `declare global` declaration must include an explicit type annotation.
|
||||
- A `declare global` declaration must include an explicit initializer.
|
||||
- `declare global` initializer analysis is dependency-graph based rather than source-order based.
|
||||
- A `declare global` initializer may depend on other visible globals only through their canonical owner identity.
|
||||
- Cycles between globals are statically invalid.
|
||||
- A global import is valid only when the imported symbol resolves through a `global` entry in `mod.barrel`.
|
||||
- Imported visible names from `fn`, `service`, `global`, and `const` must not collide with already-visible names in those same cross-category spaces; aliasing is required to disambiguate.
|
||||
- `[Init]` and `[Frame]` are valid only on top-level `fn` declarations of shape `fn name() -> void`.
|
||||
- `[Frame]` is required exactly once for an executable project.
|
||||
- `[Init]` is optional.
|
||||
- A file may declare at most one `[Init]`.
|
||||
- The `[Init]` colocated with `[Frame]` is the project init.
|
||||
- Project init must be colocated with `[Frame]`.
|
||||
- `InitAllowed` is valid only on SDK host methods and is invalid on userland `fn`, `global`, `service`, `const`, `struct`, `contract`, and callback surfaces.
|
||||
- A host method signature in a reserved stdlib/interface module MUST carry exactly one `Host` attribute.
|
||||
- A host method signature in a reserved stdlib/interface module MUST carry exactly one `Capability` attribute.
|
||||
- A `Host` attribute MUST declare exactly the named arguments `module`, `name`, and `version`.
|
||||
@@ -231,6 +250,19 @@ Rules:
|
||||
- A `BuiltinConst` declaration is not part of ordinary compile-time constant evaluation and lowers through VM-owned builtin constant materialization instead.
|
||||
- A `declare const` exported through `mod.barrel` may be imported from another module only through ordinary module import rules.
|
||||
- A `declare const` does not introduce mutable runtime storage; implementations may inline, fold, or materialize it as an immutable constant as long as observable semantics remain unchanged.
|
||||
- These `declare const` rules do not define `declare global` initializer admissibility.
|
||||
- `declare global` initializers are not general procedural bootstrap surfaces.
|
||||
- In v1, a `declare global` initializer may use:
|
||||
- primitive literals and simple value operations,
|
||||
- value-bearing member access,
|
||||
- `new Struct(...)`,
|
||||
- and reads of other globals that preserve an acyclic dependency graph.
|
||||
- In v1, a `declare global` initializer must reject:
|
||||
- top-level `fn` calls,
|
||||
- `some(...)`,
|
||||
- `none`,
|
||||
- `if`,
|
||||
- and `switch`.
|
||||
|
||||
### 3.5 Enum declarations and values
|
||||
|
||||
|
||||
Reference in New Issue
Block a user