Orkuncakilkaya
dc75a5a5ab
L1. Two vars, consts, enums, properties or events of one name in a program are an error naming both places (functions already were); the first used to win silently. A let / var of a name its own block already declared is an error (it used to shadow). A function with a result type whose body can reach its end without a return is an error, asked structurally of the body - a return, an if/else or a match with a default arm whose every branch ends - rather than handing back whatever the result slot held. The game, the lab and every package example pass all three; the lab had one harmless shadow, and the game's split screens had two real bugs of the kind. examples/rejected/ holds the four refusals, checked by the test runner's new reject_case. Seed regenerated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
8 lines
584 B
Markdown
8 lines
584 B
Markdown
bump: minor
|
|
type: feat
|
|
**A name is defined once, for every kind of declaration.** Two functions with one name were
|
|
already an error; two `var`s or `const`s (or an enum and a const), or two `property` / `event`
|
|
records, kept the first definition silently. A game lost months to it: two files both said
|
|
`KEY_LEFT`, one meaning an arrow key's code and one a binding slot, and the menus read the slot.
|
|
They are now an error that names both files and lines. `examples/rejected/` holds the two cases,
|
|
checked by a new `reject_case` in the test runner (an example the compiler must refuse).
|