Progress / May 2026

Reflection

With May behind us and a new release of v0.1.2, I figured it is a good time to reflect on what has been built so far for Talos. With this release, Talos now has some astounding functionality which includes the following:

• Full Featured Dynamic Runtime
• Baseline JIT Compilation
• Type-Checking and Extended Linting
• Modularized Project Configurations
• Extensive Integrated Tooling
• Colorless Functions via Policies
• Concurrency via Green-Threads
• Testing/Benchmarking Framework
• Runtime Decorators
• Compile-Time Attributes
• Explicit Resource Management

These are some incredible features, however many of these are still in their early stages of development. For example, the runtime is still fully dependent on the underlying type-checker. Arguably this is necessary for type-safety and correctness, however being able to run a program with the --typeless flag can be useful in some contexts. Additionally, there is much work to be done to improve the internal codebase for better language-server outputs and to make the codebase friendlier to contributors.

In reflection, Talos has some great bones for a new programming language but really needs a substantial facelift to be ready for the long-term.

Upcoming

Looking ahead, I am currently in the process of rewriting portions of Talos in my spare time with these lofty goals in mind:

• Improved AST Design  —  To facilitate language-server outputs.
• Better Formatter Support  —  To fix quirks and add more options.
• Rework Website Inputs  —  Some sections are all over the place.
• Integrate Baseline JIT  —  Attempt to prioritize JIT over bytecode.
• Decouple Module Compilation  —  Breakup compilation to be independent.
• Performant Type-Checking  —  Type-checking needs major work for performance.
• Bind Runtime to Linter  —  To accept plugins for writing linting rules.
• Abstract Scheduling  —  Necessary for customized execution policies.
• Update Foundataions  —  Implement arena-allocators, and rework foundations.

Although this will appear to be a large amount of work (and it probably is), these updates will enhance the codebase and give Talos the foundations it needs to be ready for library support. Over this next period, I plan to give monthly updates on the current progress of these rewrites. So far I have been working on the improved AST and formatter upgrades, after which I will tackle getting the foundations and abstract scheduling ready to then rebuild the runtime fully.

As for a timeline of these upgrades, I really cannot say. My ideal timeline is to have these changes ready by December for a v0.2.0 release, in which I hope to do Advent of Code with Talos. Until then, follow along with these monthly blog posts to see what progress is made!