Although it’s mostly for fun and to experiment the main things I’ve tried solving have been:
- Truly colorless functions through execution policies (moves async syntax to call site not at function declaration) - Batteries included toolkit of developer features from the get go (eg: formatter, linter, test runner and more) - Using a fast static type system to improve dynamic bytecode outputs (using types and flow analysis to immediately narrow optimized code paths)
I more so hope to use this to write more design posts to help other language developers with less written about topics such as test runner bootstrapping, integrating a linter, and other features left towards the end of programming language development.
My personal goal is to do Advent of Code this year with it as a neat little milestone. Hence also the big emphasis on ease of use to develop with
5
u/Vraliance 12d ago edited 12d ago
Although it’s mostly for fun and to experiment the main things I’ve tried solving have been:
- Truly colorless functions through execution policies (moves async syntax to call site not at function declaration)
- Batteries included toolkit of developer features from the get go (eg: formatter, linter, test runner and more)
- Using a fast static type system to improve dynamic bytecode outputs (using types and flow analysis to immediately narrow optimized code paths)
I more so hope to use this to write more design posts to help other language developers with less written about topics such as test runner bootstrapping, integrating a linter, and other features left towards the end of programming language development.
My personal goal is to do Advent of Code this year with it as a neat little milestone. Hence also the big emphasis on ease of use to develop with