Current status: need to make proper parser, currently on structuring!!!!
The semantic analysis step need to generate a new tree (code tree?), and pass this to the backend.
Code tree need to be simple enough so that we can generate libgccjit representation easily. this ages
We currently planned to generate basic structure, then generate LLVM IR that are structured with generational reference (vale thing).
Also unsafe mode will be just pure evil.
Also should resolve type.
~~Current status on the front-end: hell
Current status on the back-end: hell 2~~
We kind of finished "half-working" backend of the compiler, need:
[ ] documentation
[ ] complete type system (this needs to interact with the analyzer so how now)
[ ] memory leak fix (not that much, currently around like 500-600 bytes me not sure)
Current status of the front end is fucked, I don't know how to approach this, thinking of top-down type analysis with the coffee just a props on the backend.
Current status: need to make proper parser, currently on structuring!!!! The semantic analysis step need to generate a new tree (code tree?), and pass this to the backend.
Code tree need to be simple enough so that we can generatethis ages We currently planned to generate basic structure, then generate LLVM IR that are structured with generational reference (vale thing). Also unsafe mode will be just pure evil. Also should resolve type.libgccjit
representation easily.