Luca Antiga

> > It's not entirely clear to me what should happen here. Optionally suppress the stack trace that goes into the module? > > I think, when the code is...

You're right again, now it makes sense.

Should macros in modules be referenced in sourceMaps at all? All a source map should do is map the pre-expansion code to the post-expansion code. So adding file/module information might...

:+1:

Sounds great, a webpack workflow would be a very nice addition to ki. You should look into how the live editor on ki-lang.org does it. Specifically, take a look at...

ki macros are a thin layer on top of sweet.js macros - they are not real lisp-style macros. Take a look at the `ki macro` [entry in the API](http://ki-lang.org/api.html) as...

Right now mori functions are made namespace-globals by default in all namespaces, so you have access to constructors and the mori API. In fact though, the only place where mori...

Yes, this is a known limitation, at least for now. Keywords cannot be evaluated in ki as they are in Clojure, you should use `get` in the meantime: ``` ki...

The `keyword` function currently returns a ClojureScript keyword object. We could indeed make `keyword` return a function and attach all properties of the keyword object to it (making it callable...

See also #10