Unify beginner syntax while preserving compatibility, repair ownership and parser guards, add verified distribution tooling and VC6 Windows 98 build inputs, and clarify documentation and release status. Preserve DOS build-input line endings and exclude generated binaries/caches.
883 B
883 B
Claro Performance and Optimization Notes
Current release: Claro v2026.10.20.223203
Performance work should come after language behavior is stable and measured. Do not optimize blindly.
Current priority
Claro's current priority is correctness, accessibility, friendly diagnostics, and reliable beginner examples.
Before optimization work
Add:
- small benchmark scripts
- expected-output checks for benchmark examples
- a timing command or repeatable timing script
- documentation for what is being measured
Optimization rules
- Keep beginner-visible behavior unchanged.
- Measure before and after every optimization.
- Prefer simple interpreter cleanup before complex compiler architecture.
- Do not add bytecode, JIT, or advanced compiler stages until the v1 semantics are stable.
See also:
ROADMAP.mdCURRENT_STATUS.mdFUTURE_FEATURES_ROADMAP.md