requier, although I had a plan to fix that & I think I wanted to make sure I would not introduce more dependncies that would prevent me from that.
@Gozala I also imagine it should be easy to have an option to toggle including macros (and their dependencies) being included in the compiled output or not? This could be either a compiler option, or per-module and/or per-macro flag (via metadata)... I can certainly see how a Wisp library which is distributed in its compiled form would want to make its macros available without having to recompile the whole library every time
That actually reminded me another idea I had, which was to generate two outputs when file with macro definitions was passed like
module.macros.js so that macro definitions won’t tax the generated js, but would still make it available, alternative would be to let compiler either emit file with macros or file with actual js so you could create two outputs or one.
Cannot call method 'apply' of undefinedand fail because Node says
Cannot read property 'apply' of undefinedinstead?
def. Is there anything in particular which makes this behavior unfeasible for Wisp?
defused for declaring locals? :-)
defregardless of where it’s run into
def’s in wisp
letso I never bothered fixing it.
ReferenceError: sum is not definedfor
(+ 1 1), for example
nsalso seems to be undefined, so I'm unable to bring functions into the namespace to use in the repl
wisp.sequencenamespace when I was running from a random directory with globally-installed wisp
npm install wisp, it worked out (still running repl via globally-installed)
undefinedas it’s a macro so that could have confused you as well