Home /Modules/api/SYNTAX-VERSION-MATRIX.md

SYNTAX-VERSION-MATRIX.md

api/sleela/2.1/language/SYNTAX-VERSION-MATRIX.md · 61 line(s) · markdown

SLeeLa Syntax Version Matrix

The version declared in a source file (for example, #sleela 2.9) is the language syntax version, not the Sleelvac compiler release number. The normative grammar is SLEELA.syntax; the compiler gate is implemented in impl/frontend/version.{h,cpp}.

The compiler currently accepts source syntax 1.0 through 3.1 and defaults unversioned source to 3.0 with a warning. Syntax 3.0 consolidates the established 1.x/2.x language surface into the current normative edition; it adds no new grammar production solely through the edition bump. A newer compiler does not silently upgrade an older source file: each feature remains subject to its own syntax-version gate.

Syntax versionDocumented featureNormative referenceStatus / boundary
1.8Inferred local declarations with let; constructor arguments on new Type(args)SLEELA.syntax, §12Constructor overload resolution and this(...) / base delegation are not verified and are rejected.
1.9Contextual GC-hint assignment: x = gc N; and x = mem N;SLEELA.syntax, §13; GC-hint APIRuntime cleanup requests, not guarantees of immediate reclamation; reachable objects remain valid.
1.10Two meanings of extends: class inheritance and document-level groupingSLEELA.syntax, §14; EXTENDSKeep the class and document forms distinct.
1.11One level of nested classesSLEELA.syntax, §14Maximum lexical nested-class depth is two including the enclosing class.
2.2Generic type signaturesSLEELA.syntax, §16Type parameters on classes/methods, parameterized types, and wildcards; earlier 1.3–1.11 surface is carried forward.
2.3Philosophers Guide-chain expression new T(...) :: Guide :: Guide ...SLEELA.syntax, §17Normative language construct; consult implementation and tests for current execution coverage.
2.4author / authorial document markerSLEELA.syntax, §18Compiler-active: permits duplicate members in marked documents and emits originated-source branding.
2.5material and memory document markersSLEELA.syntax, §§19–20Declarative document claims; no parsing, typing, dispatch, or code-generation effect.
2.5Wide signed integer primitives: long, int64, int128SLEELA.syntax, §21Signed-width behavior is described in the normative specification; do not infer arbitrary-precision arithmetic from the larger named widths.
2.6Keyword supporter documentsSLEELA.syntax, §22Links occurrences of selected control-flow keywords to supporting documentation; additive annotation behavior.
2.6determine, object, and field document markersSLEELA.syntax, §§23, 26Declarative markers. object has the additional 2.8 reification standing described in §26.6.
2.7Base-2 signed integer series: int32 through int16777216SLEELA.syntax, §24Named signed widths; actual arithmetic capacity remains bounded by the implemented native value slots.
2.8Base-2 unsigned integer series: uint32 through uint16777216SLEELA.syntax, §25Positive-only unsigned widths; operands must satisfy the specified unsigned typing rules.
2.8Reified standing of the object document markerSLEELA.syntax, §26.6The marker is gated from 2.6; its catalogue/reification standing is specified from 2.8.
2.9@mix consequent fieldsSLEELA.syntax, §28Repeated same-named instance fields marked @mix form an indexed group. Automatic indexes follow declaration order; explicit index lists must match the number of fields.
2.9 (future proposal)prestige document markerSLEELA.syntax, §27Not implemented. Its appearance in a 2.9 specification does not make it an accepted compiler feature.

Document-marker catalog

The document-scope marker family is summarized in DOCUMENT-MARKERS.md. The author marker is the compiler-active exception; the other catalogued markers are declarative and must not be described as changing runtime behavior.

Compatibility rules

Syntax 3.1 edition status

Syntax 3.1 is the current specification edition and the compiler's accepted ceiling. It consolidates the earlier language surface without changing the minimum version required by any historical feature. The 2.9 @mix feature remains gated at syntax 2.9. The §27 prestige marker remains a future proposal and is not made valid by the 3.1 edition. See the normative syntax specification.