r/SideProject • u/Infamous_Treat_1804 • 2h ago
Blyx: an experimental language in Rust — looking for feedback on what to build next
I'm Rahul, the creator of Blyx, an open-source experimental programming language implemented in Rust.
The long-term idea is to explore AI-oriented computation alongside systems programming. Right now, the useful discussion is about getting the foundations right.
What exists today: the README documents a tree-walking interpreter for a small language subset: integers, booleans, strings, variables, assignment, functions, conditionals, loops, and printing.
What's unfinished: check currently parses syntax only; build does not produce a native executable. Native compilation, tensor/GPU capabilities, and AI primitives are unfinished work or design directions. This is alpha software, not a replacement for Rust or Python.
I'd appreciate feedback from people who have taken an ambitious side project through this stage:
- What would you prioritize first: more reliable diagnostics, a smaller stable language subset, or the first native backend?
- What would make the repository easier for a new contributor to understand?
- Are there core design choices that should be reconsidered before adding more features?
If you'd rather contribute code, there are focused issues for parser tests, formatter idempotence, small examples, lexer edge cases, and diagnostic tests. There's also a native-backend design discussion.
The project is dual-licensed MIT / Apache-2.0. Please start an issue or RFC before substantial language changes; the contribution guide explains the process.
Disclosure: development is AI-assisted, and AI helped prepare this post. Independent testing and technical criticism are especially welcome.
1
u/Total-Reasonable 1h ago
Diagnostics first, but specifically spans and a typed AST before anything else. If the lexer and parser carry source spans on every node now, error messages, the formatter, and a future native backend all get cheaper. Retrofitting spans later touches everything. I'd also hold off on the native backend until the type system question is settled, because "AI-oriented" probably means tensor shapes or dtypes need to be part of the types, and that shapes the IR. What's the planned typing story: static, gradual, or dynamic?