kit

I don't know about a list online but here's what I know off, in the C/C++ realm Odin - https://odin-lang.org/ Zig - https://ziglang.org/ Beef - https://www.beeflang.org/ Jai (not public yet) - [1] Carbon (C++) - https://github.com/carbon-language/carbon-lang D Lang - https://dlang.org/ Rust - https://www.rust-lang.org/ cppfront (Herb Sutter's C++ frontend/syntax) - https://github.com/hsutter/cppfront Nim - https://nim-lang.org/ Crystal (not sure if this counts) - https://crystal-lang.org/ Vale - https://vale.dev/ Hylo (formerly Val, just found it now) - https://www.hylo-lang.org/ Vala (compiles to C, some GTK apps are written in this) - https://vala.dev/ C3 - https://github.com/c3lang/c3c Rune (last commit 7 months ago) - https://github.com/google/rune Kit (dead, last commit 5 years ago) - https://github.com/kitlang/kit There's probably m

I like how clean the lexer is: https://github.com/kitlang/kit/blob/master/src/Kit/Parser/Le...

>designed with game development in mind What design decision and features were made according to that? Basically, what "designed for game development" means? Also checking the commit history, first commit [1] says that it is after a rewrite in Haskell. What was the original language and why made the change? [1]: https://github.com/kitlang/kit/commit/4d3de98f218f2427529ac4...

Second this. I'm writing a compiler now (https://github.com/kitlang/kit) and this book has been invaluable. A few other tips: * Use a parser generator. Parsing is more or less a solved problem; get it out of the way as fast as possible. * Writing a language that compiles to another language is very helpful as you can often borrow the underlying language's implementation of a feature. Doubly helpful if you can leverage the underlying language's libraries for things like syscalls. * Make a todo list (I like Trello for this) full of self-contained tasks. Pick one at a time, think through how you would implement that feature, and go to work. Compilers look like a lot of work in the beginning, but if you take one step at a time, one day you'll look back and have accomplished more than you realize. The list can also be helpful to avoid scope cr