Implement the base

[thi8v]

Here is the list of things related to the language, that is needed to be implemented for the v0.1.0 milestone. And with there own RFC, -> #22

• Function definition, declaration, and call #40
  • return statement
• var and const #41
• operators + unary expression -> Tracking Issue for Operators #47
• control flow
  • if / else if / else
• loops
  • for loop -> not sure what they will be, an issue will be created when i know
  • while loop
  • loop loop -> use less, it just add a new keyword, use while (true) { .. } instead.
  • continue statement -> expression
  • break statement -> expression
• comments -> Add support for comments #14
• primitive types -> Type checker and type inference  #10
• remake blocks, no more 'automatically' returned expr, and the semicolon necessary : move sc parsing in stmts and make them optional for some expression instead of forbidden and make list expr { expr, expr, expr, ... }
• defer statements -> will be done in another version. Their is things more important for now
• remake call expression -> from $ident(...) to $expr(...).
• .* deref operator and right unary operation
• member access expr a.b
• string expr literal
• char expr literal

[thi8v]

For the code generation and compilation (LLVM related crates), in the Zom compiler. We could replace it with the C++ library, because it's the official way to use LLVM, there is some issues in this project that is related to LLVM not working : #24, #20, #23, #21. If we replace it with an a C++ package, we could just follow the doc and not wasting its time to found the function in Inkwell, etc ..

Pros

• We can follow the LLVM docs without any trouble to find the corresponding function in Inkwell
• Some issues (Fix the CI #24, Fixing builder #20, Impl llvm #23, CI bug #21) could be solved.

Cons

• Safety, C++ is safer than C but C++ is not safe as Rust is.
• Some layer between Rust and C++ is needed, you can find some solution below,

Solution N°1

Write a serializer that serialize the result of the type checking (or the end of the compilation pipeline that doesn't need LLVM). And the C++ program will be executed in a child process, with the serialized input, and we deserialize and return the output desired by the compiler.

Solution N°2

Write a C++ lib that uses LLVM and emit the desired output by the compiler, and his functions is called by the the Zom compiler with the Rust FFI to C++.

[thi8v]

Done.