This language, is called HolyLang, currently I am working on the bootstrap phase of it.

It is written in pure Rust, with 0 dependecies. Handmade simple recursive-down parser and developed paranoidly with defensive coding techinques.

Additionally, for the parser and semantics layers, I have over 100% unit test coverage, not just lines covered, but also regions, functions and branches covered! Extremely time consuming, but worth it.

README:

HolyLang is more secure than Rust, but not as performant as Rust. The purpose of HolyLang is divine security, not speed.

• HolyLang has readable syntax, and semantics. That is a security feature in its own because readable code = auditable code = maintainable code = probably secure code.
• HolyLang has no borrow checker, and yet is still more secure than Rust. programs can be easily reasoned about due to the simple binary safey model of “move, or copy”.
• HolyLang arithmetic is always checked, including bitwise. Floating point arithmetic is also always checked.
• HolyLang has no warnings, only errors. Unreachable code? Error. Unused variable? Error. Etc.
• HolyLang forces documentation for functions, structs, and constants.
• HolyLang has no type inference, everything must be explicilty stated.
• HolyLang does not allow overshadowing at all. Making codebases look cleaner, and reducing likelyhood of logic bugs.
• HolyLang lock and unlock statements allow you to declare “zones” where variables behave as constants, dynamically.
• HolyLang’s bootstrap compiler transpiles down to pure Rust for a mathematical guarantee of safety: "If Rust is safe, then HolyLang must also be at least as safe as Rust".

.. and a lot more! This is just the bootstrap compiler, the actual compiler will have even more security features, such as static stack analyzes that guarantee (at compile-time!) a program cannot overflow the stack, allowing for even stricter security than Rust, and even other formally verified languages like Ada SPARK, whom have no stack overflow protection.

I already have compiler warnings as errors, but, I still haven't integerated clippy yet, so code base is certainly going to get very cleaner as soon as I am finished with the PR I am working.

Any feedback on syntax/ semantics, whatever, is welcome. Also contributions are welcome

2 posts - 2 participants

Read full topic