Nathan Faubion

It does work, but it also means all hook code must be written with a polymorphic region, with the restrictions that come with that (`$` and `#` not working intuitively)....

Interesting. It seems like there's a test that covers this, but maybe the newtype is messing with it. https://github.com/natefaubion/adt.js/blob/master/test/macros.sjs#L69 If macros are your thing, I'd suggest you checkout https://github.com/natefaubion/adt-simple which...

It is a pretty printer for the internal language. All frontends require pretty-printing of some sort. This could be more specific.

There are two main components to matches: The DSL, and the dispatcher. Which one do you consider to be the "engine"? The DSL and dispatcher aren't really coupled, as you...

The lowest level you can get is the code generation. Unlike the flatiron validator, which I assume inspects the schema object each time its called, matches has to compile a...

Honestly, the AST is about as simple as it can get. I think there are a few references to 'pattern' in the compiler, and it may not strictly be necessary...

One thing I've wondered is how we play well with the wealth of CommonJS modules, which aren't going to follow the ES6 `import` syntax, and don't need to be read/expanded/parsed/evaled,...

I've been poking around, trying to get a feel for how we should move forward with modules. Unfortunately, there's no easy, clear, or even straightforward way. I'd like to expand...

> What's the latest thinking on this? AFAIK, sweet inside ES6 module-syntax breaks things since the export keyword is shared by the two? i.e. if you transpiler first, you lose...

ES6 supports `import 'somemodule'` syntax specifically for side effecting imports. We shouldn't arbitrarily change module semantics for compile time code.