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
Currently, we use empty type application to represent in-scope references. This poses some problems when resolving specialisation references in the extendContext and inside each backend.
A solution to this would be to incrementally build the context from the list of previous definitions:
(name bit (+ 1 1))
(name byte (* bit bit bit bit bit bit bit bit))
would be represented as:
Vect 2 (TDef' 0 True)
and the first step of compilation would map this structure to
Currently, we use empty type application to represent in-scope references. This poses some problems when resolving specialisation references in the
extendContext
and inside each backend.A solution to this would be to incrementally build the context from the list of previous definitions:
would be represented as:
and the first step of compilation would map this structure to
Just like a typical compiler would add variable declaration to the context.
The text was updated successfully, but these errors were encountered: