#Design Docs

Rationale documents explaining why WESL features are designed the way they are. These accompany the specification in the wesl-spec repository.

#Design Rationale

• Designing WESL — Goals, priorities, and audience considerations guiding WESL’s design
• Imports Design — Wildcard import tradeoffs and the @! module attribute form
• Visibility Design — Why three visibility levels, why package by default, why re-exports cannot widen
• Conditional Translation Design — Design rationale for structured @if vs unstructured #ifdef

#Historical Discussions

• Import syntax discussion
• Community use of WGSL string interpolation
• Plugin design ideas
• Old generics discussion
• Packaging design
• Use.GPU ideas with unconed
• Meeting notes 2024.09