ludic/examples/rejected/duplicate_const.ludic
Orkuncakilkaya dc75a5a5ab feat(lang): a name is defined once, a local once per block, and a result is always returned
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>
2026-09-23 23:55:20 +03:00

8 lines
391 B
Text

# duplicate_const.ludic - two files that both define KEY_LEFT. The compiler refuses it and names
# both places; it used to keep the first silently, and a game read an arrow key as a binding
# slot's number for months. (Rejected on purpose: tools/ludic-cli/test.ludic, reject_case.)
program DuplicateConst {
const KEY_LEFT: int = 130
const KEY_LEFT: int = 2
entry { print(KEY_LEFT) }
}