docs: tuple syntax cutover — Tuple(...) type, .(...) value, channel-outside-Tuple failables
Rewrite specs.md tuple/failable/pack/UFCS/grammar sections to the new syntax, update readme.md, and refresh stale tuple references in example header comments. Also fixes two pre-existing doc inaccuracies surfaced in review: drop the value-discarding `;` in the tuple-return examples, and correct the §13 function-type grammar production (optional param list + optional trailing `!` channel). Optional semantics unchanged. current/CHECKPOINT-LANG.md logs the cutover.
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
// A tuple literal used in a type position (`(i32, i32)` reinterpreted as a tuple
|
||||
// type at a type-demanding site like `size_of`) must list only types. A non-type
|
||||
// element — here the `1` in `(i32, 1)` — is rejected with a user-facing
|
||||
// A tuple type (`Tuple(i32, i32)` at a type-demanding site like `size_of`) must
|
||||
// list only types. A non-type
|
||||
// element — here the `1` in `Tuple(i32, 1)` — is rejected with a user-facing
|
||||
// diagnostic instead of silently fabricating an `i64` field for that slot.
|
||||
// Regression (issue 0067).
|
||||
// Expected: a clean "tuple type element is not a type" error at the `1`; exit 1.
|
||||
|
||||
Reference in New Issue
Block a user