axyolotl / voxu

🧊 A strongly and statically typed, memory-efficient functional programming language.

🧊 voxu

A strongly and statically typed, memory-efficient functional programming language.

This is the repository for the compiler, lexical analyzer and parser, and the standard library for the Voxu programming language. It is worth noting the language itself isn't even near completion for now, so it is all right to write everything in a different language and then migrate it to Voxu once it is ready.

It's fair to tell newcorners about the fundamentals, concepts, design decisions, and of course, the purpose and semantics of Voxu, while it is still in its early stage.

For that reason, this document is written in a way that is easy to understand, and is intended to become a reference or formal specification of the language as it evolves.

As this is still in its first moments, I would like to hear your feedback and suggestions, so feel free to contact me at:

• Discord
• The issues of this repository

At long last, Voxu is still my first programming language ever, so I'd appreciate any help or advice anyone can give me, as I love to learn new concepts and listen to feedback.

📖 Table of Contents

• 🐏 Memory efficiency
• 💪 Strong and static typing
• 🌍 Functional programming
• 🏁 Standard library
• ♟️ Macros
• ⚙️ The compiler
• 🎏 Syntax and semantics

voxu's Issues

Question: How can all variables have their value calculated at compile time?

https://github.com/axxxyyy/voxu/blob/7398861ad6149a4d6827c33f06811063d9577557/wiki/memory-efficiency.md?plain=1#L52

This claim is very hard to believe. Are you calculating every possible value of a variable at compile time? Would this not lead to explosive binary size?