> > Hmm, so the reason that macros are able to function is that they occur > before type computation?
I don't know how best to respond to this question, but I will throw out that staged functions are expanded after type information is known to the compiler. On Friday, July 10, 2015 at 10:07:23 AM UTC-4, Brandon Taylor wrote: > > Hmm, so the reason that macros are able to function is that they occur > before type computation? One solution might be to make scope annotations > that override defaults. Then, when eval is called, it optionally attaches > scope annotations to a given scope. Note that scope annotations should be > able to refer not only to regular scopes but also indexed items like dicts > and dataframes. Wait, how does eval handle type computation if it occurs > after type computation? > > On Friday, July 10, 2015 at 5:51:05 AM UTC-4, Fabian Gans wrote: >> >> Hi Cedric, >> >> a macroexpand shortcut for the REPL shouldn't be a big problem, I just >> tried to prototype one and it seems to work fine: >> https://github.com/meggart/julia/commit/73c96897572cedf10f74fd09907232c706bbdf48 >> >> Is there any special functionality/problems which I don't see that should >> be considered? >> >> >> >> >>
