You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Constructor calls are currently represented by PureApp nodes in the core tree and following representations.
This would be a bit more symmetrical to how the introduction and elimination of codata/objects (new) is treated.
Note that optimizations (case-of-known-case etc.) are currently possible without making constructors explicit, since we can just compare the symbols.
This works, since free variables in core (such as data types and constructors) are not renamed (which is the case for bound local variables) and the PureApp and the Match thus still point to the constructor symbol.
The text was updated successfully, but these errors were encountered:
Constructor calls are currently represented by
PureApp
nodes in thecore
tree and following representations.This would be a bit more symmetrical to how the introduction and elimination of codata/objects (
new
) is treated.Note that optimizations (case-of-known-case etc.) are currently possible without making constructors explicit, since we can just compare the symbols.
This works, since free variables in
core
(such as data types and constructors) are not renamed (which is the case for bound local variables) and thePureApp
and theMatch
thus still point to the constructor symbol.The text was updated successfully, but these errors were encountered: