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
This should yield a phase error during the typing phase. A toplevel splice in a macro implies more than two execution phases (~A.m is of phase 2) whereas currently we only support two phases (0 and 1).
While having more than two phases makes conceptual sense, there would be a complexity cost in supporting it (an unknown number of top-level splice execution and replacement stages, instead of just one).
I'm inclined to think about that as we have two phases (compile-time and runtime) but multiple levels. Perhaps it wouldn't be right to think about that as a phase 2 computation anyway, as it is not necessarily evaluated before all 1 phase programs.
a.ml
:b.ml
:bug:
The text was updated successfully, but these errors were encountered: