[FEATURE REQUEST] Refactoring of NativeCall
s
#140
Labels
‼ priority:p1
Priority planning - level 1
🎊 resolution:resolved
Bug or feature resolved - might not have been merged to master yet
🎆 type:feature
New feature or request
🛠 type:refactoring
Refactoring of the codebase
Milestone
Description
While the idea of supporting language constructs through
NativeCall
s seemed appropriate, the only difference from "regular" expressions is that it was easier to support n-ary expressions. We should removeNativeCall
s entirely and transform them intoExpression
instances.After this, we should add a generic
NaryExpression
that serves as a base class for what we are now supporting through native calls.As a final note, to make expression evaluation more generic, we should also add the option of changing the evaluation order of the parameters of an expression: imposing left-to-right recursive evaluation, as well right-before-left evaluation in assignments, is too restrictive.
The text was updated successfully, but these errors were encountered: