- Stellenbosch, South Africa
- https://deavmi.assigned.network
-
I ❤️ programming and computers. I have a big interest in compiler and interpreter design and implementation and also an interest in networking and fmts/protos.
- Joined on
2021-12-21 -
-
🔴 Note: This is done, just needs inspection
TypeChecker
- Improved the code for handling
FunctionCall(function calls) - Removed the pushback
Actually, mmh, this could be sorted out in the dependency generation - now that I think about it.
Actually pushback can be removed, it was the loop condition/structuire that caused us to have to handle it. itwas a tail-end (about-to-exit) cleanup
So it seems that just removing it won't work, but maybe it should be there? I only had this whole "remove pushbacks" because variables were being done wrong way way back (which has since…
So it seems that just removing it won't work, but maybe it should be there? I only had this whole "remove pushbacks" because variables were being done wrong way way back (which has since…
Resolver
resolveWithin_Safe()now does expected types as wellResolver (unittests)
- Added testing for the safe resolution methods
Local unittests ✅
CI/CD ✅
Resolver
resolveWithin_Safe()now does expected types as well
Resolver (unittests)
- Added testing for the safe resolution methods
Dependency
- When resolving a
FunctionCall'sFunctionuse the safe resolver - When resolving a
VariableExpression'sVariableuse the safe resolver - When resolving the `VariableAssignm…
Will commit and push the usage cases of this later, need a break now.
Resolver
- Added
resolveBest_Safe(...)
ResolutionError
- Added new type