Expression use analysis
Registered by
Allen Short
E's expander can emit different expansions for an expression depending on the context it's used in: for value, for effect, or for control. This is only used in a few expansions, but making this distinction in the compiler can result in better code generation.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)