989e18b760
Replace the bare-paren tuple grammar with explicit, position-unambiguous
forms, mirroring how structs work:
type `(A, B)` -> `Tuple(A, B)` (named keeps `:`)
value `(a, b)` -> `.(a, b)` (named uses `=`)
typed (new) -> `Tuple(A, B).(a, b)` (like `Point.{...}`)
failable `-> (T, !)` -> `-> T !`
`-> (T1, T2, !)`-> `-> Tuple(T1, T2) !` (channel outside Tuple)
Bare `(...)` is now grouping only, everywhere; a comma in bare parens is a
hard error with a migration hint. Grouping, function types `(A, B) -> R`,
param lists, lambdas, and match bindings are unaffected.
`Tuple(...)` is strictly a TYPE in every position (including `size_of` /
`type_info` args); a tuple VALUE comes only from `.(...)` (anonymous) or
`Tuple(...).(...)` (explicitly typed). A bare `Tuple(1, 2)` is a tuple
type with non-type elements -> rejected.
The ~110 tuple-bearing corpus files were migrated with a one-shot
AST-aware migrator (the `sx migrate` tool from the prior commit, removed
here). New examples: 0130 (new syntax), 0131 (typed construction), 1060
(named-tuple failable return). 1116 golden updated for the new hint text.
14 lines
548 B
Plaintext
14 lines
548 B
Plaintext
// 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
|
|
// 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.
|
|
|
|
#import "modules/std.sx";
|
|
|
|
main :: () -> i32 {
|
|
print("bad tuple type size = {}\n", size_of(Tuple(i32, 1)));
|
|
0
|
|
}
|