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.
20 lines
646 B
Plaintext
20 lines
646 B
Plaintext
// Value-carrying `catch` rejection (ERR step E2.1b): when the failable LHS
|
|
// carries a value, a non-diverging catch handler must produce a value of the
|
|
// success type — a value-less (void) body is a type error (otherwise the
|
|
// success and error paths couldn't merge to one value). Diverge instead
|
|
// (`return` / `raise`) or yield a value. Positives: `examples/229-value-failable-consume.sx`.
|
|
|
|
#import "modules/std.sx";
|
|
|
|
E :: error { Bad }
|
|
|
|
parse :: (n: i32) -> i32 !E {
|
|
if n < 0 { raise error.Bad; }
|
|
return n;
|
|
}
|
|
|
|
main :: () -> i32 {
|
|
x := parse(-1) catch (e) { print("oops\n") }; // error: body yields no value
|
|
return x;
|
|
}
|