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 they are transformed in source order, which necessitates using scope activation/deactivation jugglery -- not a big deal, but it is unnecessary complexity anyway; if funs are saved in a scope slot before transformation begins (that is, saving must occur while parsing), the transformer can simply start off by transforming declarations saved in the fns slot of every scope the transformer enters; in other words, anything hoisted in a scope should get transformed first; in other words, again, source elements should get transformed based on their semantic position rather than their source location; this will also make things easier when the notion of "active-after" indices are brought into use, helping shake/shave any modifications happening after the side-effect has been executed.
The text was updated successfully, but these errors were encountered:
currently they are transformed in source order, which necessitates using scope activation/deactivation jugglery -- not a big deal, but it is unnecessary complexity anyway; if funs are saved in a scope slot before transformation begins (that is, saving must occur while parsing), the transformer can simply start off by transforming declarations saved in the
fns
slot of every scope the transformer enters; in other words, anything hoisted in a scope should get transformed first; in other words, again, source elements should get transformed based on their semantic position rather than their source location; this will also make things easier when the notion of "active-after" indices are brought into use, helping shake/shave any modifications happening after the side-effect has been executed.The text was updated successfully, but these errors were encountered: