You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: refresh language spec to v0.7 and discover spec path in tests
Fold the recent surface additions (`?` on Option, default params,
constants, tuples, list slice patterns, #lower_name, generated-namespace
isolation) into the spec, bump the version to v0.7, and replace the
historical changelog blocks with a current "Implemented surface" status
index plus the existing future-directions section.
Tests no longer hard-code the spec version: a common helper discovers
docs/RSScript_v*_Spec.md (and the package-manager design doc) by name
shape, and the dynamic-dispatch assertion is version-agnostic.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -208,7 +208,7 @@ The product core is the review protocol: `.rssi` semantic contracts, structured
208
208
209
209
Before AI, writing code was expensive and reviewing was manageable. That ratio has flipped: generating is cheap, reviewing is the bottleneck. RSScript is designed for the new ratio: AI writes, the compiler checks semantic boundaries, humans focus on the *risk*. What mutates, what gets retained, who owns a resource, where you cross into native or unsafe, what changed in a public API — all of it lives in the signature and in machine-readable diagnostics.
210
210
211
-
This discipline is binding, not aspirational: the language specification opens with a [Constitution](docs/RSScript_v0.6_Spec.md#constitution) of nine articles that govern every design decision — most importantly that constraint is the product, that review-critical behavior must be explicit in the signature, and that a feature is admitted only if it phrases as a reviewer question and needs no implicit rule to be ergonomic. Restraint is anchored to a measurable property (review cost), which is what keeps it from eroding as the language grows.
211
+
This discipline is binding, not aspirational: the language specification opens with a [Constitution](docs/RSScript_v0.7_Spec.md#constitution) of nine articles that govern every design decision — most importantly that constraint is the product, that review-critical behavior must be explicit in the signature, and that a feature is admitted only if it phrases as a reviewer question and needs no implicit rule to be ergonomic. Restraint is anchored to a measurable property (review cost), which is what keeps it from eroding as the language grows.
0 commit comments