Specify export renaming onto a temp target #39

Closed
opened 2026-07-03 00:41:08 +00:00 by toph · 1 comment
Owner

export { .m as ._t } $i currently lands ._t bypassing the ! shadow validation entirely (temp targets always replace). That is consistent with temp semantics — temps rebind freely — but the spec only forbids temps as export sources (§5a) and says nothing about temp targets.

Decide and write it down: either bless the behavior with a sentence in SPECIFICATION.md §5a, or reject temp targets in export lists. One-line change either way; the gap is the spec silence, not the code.

Follow-up to #35.

`export { .m as ._t } $i` currently lands `._t` bypassing the `!` shadow validation entirely (temp targets always replace). That is consistent with temp semantics — temps rebind freely — but the spec only forbids temps as export *sources* (§5a) and says nothing about temp *targets*. Decide and write it down: either bless the behavior with a sentence in SPECIFICATION.md §5a, or reject temp targets in export lists. One-line change either way; the gap is the spec silence, not the code. Follow-up to #35.
Author
Owner

For the exact snippet export { .m as ._t } $i I'd just recommend ._t = .[$i m]. But since I don't see anything wrong with someone wanting to do this, it's blessed behavior.

For the exact snippet `export { .m as ._t } $i` I'd just recommend `._t = .[$i m]`. But since I don't see anything wrong with someone wanting to do this, it's blessed behavior.
toph closed this issue 2026-07-03 18:45:42 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
toph/beloch#39
No description provided.