Status: Authoritative Specification Version: 2.0.0 Last Updated: 2026-07-15 Related Documents: 08 Milestones · 00 Master Architecture
- Cargo workspace layout in Rust.
- Set up CI pipeline.
- Implement
techscript_errorsdiagnostic and span mapping. - Implement
techscript_aststructures matching v2.0 design.
- Implement
TokenKind(including deprecatedFun). - Hex/bin/octal literal parsing with underscores.
- F-string mode stack.
- Unicode support and file extension checks.
- Parse variable declarations (
make,const), loops (each,repeat,while), and block statements. - Parse
attempt/catch/throwand module imports.
- Pratt parser for expressions.
- Parse
buildfunction declarations and lambdas. - Parse
modeldeclarations containingbuildand deprecatedfunmethods. - Snapshot tests for grammar structures using
.txstest files.
- Lexical Scope Frame stack.
- Hoist declarations in Pass 1.
- Scope checks, duplicate declarations, const assignments, and method keyword validation (
W0015warnings).
- Implement
Valuevariants andEnvironmentvariable lookup. - Expression and statement execution.
- Truthiness, float promotion, and list/map slice/indexing.
- Function call frames, closures, and recursion.
- Instantiation and method invocation.
attempt/catch/throwexception signals.- Standard collection methods.
- CLI subcommands (
run,repl,check,fmt,lint,test,new,version,help). - Auto-fixing of deprecated keywords.
- Release:
v2.0interpreter release.
- Weeks 9–10: Implement
math,string,file(targeting.txsextensions),time,random,json, andcollectionsmodules. - Week 11: Implement
webpage-builder standard library module. - Week 12: Implement
tech fmtandtech lintauto-fix integration. - Week 13: Implement LSP (Language Server Protocol) with diagnostics, autocomplete, hover details, and go-to-definition.
- Week 14: Hardening, cross-platform validation, and final v2.0 production release.
- Week 15: Design stack bytecode instructions.
- Weeks 16–17: Implement AST-to-bytecode compilation and execution VM.
- Week 18: VM stack frames and value allocations.
- Week 19: Tracing garbage collector implementation.
- Weeks 20–21: Closures, models, and optimization.
- Week 22: v2.1 release (Bytecode VM).
- Weeks 23–24: LLVM bindings using
inkwell. - Weeks 25–28: Emit LLVM IR for variables, control flow, functions, and closures.
- Weeks 29–30: GC integration.
- Weeks 31–33: Compiler optimizations (O0, O1, O2).
- Week 34: v3.0 release (Native compiler).
- Package manager implementation (
tech install,tech publish). - v3.1 release (Ecosystem package manager).
- Port frontend (lexer, parser, sema) and VM compiler to TechScript.
- Bootstrapping and validation.
- v4.0 release (Self-hosted compiler).
gantt
title TechScript 2.0 Development Roadmap
dateFormat YYYY-MM-DD
section Phase 1: Frontend
Project Bootstrap :2026-08-01, 1w
Lexer :2026-08-08, 1w
Parser :2026-08-15, 2w
Semantic Analyzer :2026-08-29, 1w
Interpreter :2026-09-05, 2w
REPL + CLI :2026-09-19, 1w
section Phase 2: Stdlib + Tools
Standard Library :2026-09-26, 3w
Formatter + Linter :2026-10-17, 2w
LSP Server :2026-10-31, 1w
v2.0 Release :milestone, 2026-11-07, 0d
section Phase 3: VM
Bytecode VM :2026-11-14, 8w
v2.1 Release :milestone, 2027-01-09, 0d
section Phase 4: LLVM
LLVM Backend :2027-01-16, 12w
v3.0 Release :milestone, 2027-04-10, 0d
section Phase 5: Ecosystem
Package Manager :2027-04-17, 6w
v3.1 Release :milestone, 2027-05-29, 0d
section Phase 6: Self-Hosting
Self-Hosting :2027-06-05, 16w
v4.0 Release :milestone, 2027-09-24, 0d
- Milestone dependencies: The roadmap prioritizes 100% v1 syntax compatibility inside Phase 1 (weeks 1–8) and Phase 2 (weeks 9–14), validating code logic using v1 test suites before proceeding to VM bytecode compilation.
- Legacy
.techimports fail in Week 5 (Semantic Analyzer).
- Renaming scripts to
.txsis required before Week 8 (CLI run commands) or Week 12 (automated format tests). - Automated formatter tests verify output parity:
tech fmt tests/ --check
- Decoupled execution phases: Scheduling standard library implementation and formatter/linter tasks after interpreter correctness is verified prevents double-work when refining syntax rules.
- v2.1: Week 15 starts bytecode compilation research.
- v3.0: Week 23 starts LLVM native IR generation.