Tim Disney

The concern I have about allowing the language consumer to do arbitrary composition is that readtables are not a monoid (they are not associative) and they don't commute. Having order...

Oh wait, they are associative aren't they? Regardless, ordering matters so my point still stands.

> I think what you're getting at is that a user of composable languages would have to be nearly as sophisticated as a developer of languages and have knowledge of...

> To be clear, a language module must have a read function as default export. Optionally, it can expose >= 1 readtable and whatever else it wants. Correct? I think...

Here's a minimal repro: ```js syntax let = function (ctx) { let params = ctx.next().value; return #`(${params} => 1)`;}; let (a) ``` Something wrong converting a `RawDelimiter` to a paren...

I just ran into a potentially similar problem with `new`: ```js let f = x => new C(x) ``` throws an error but ```js let f = x => {...

@gabejohnson I think that's totally reasonable. We'd probably be fooling ourselves if we thought we could get away without some iteration on the API anyway. We should be sure an...

@samuelgoto correct. Readtables were exposed in version 0.7 and then went away in the 1.0 rewrite. @gabejohnson has been working on their replacement. Like this issue mentions, Sweet is currently...

> In the interim, is there a quick hack that you'd recommend to access them (forking and digging in is an option, but sounds undesirable/brittle)? Yeah, the reader is being...

Syntax bindings (both `syntax ...` and `operator ...`) allow identifiers, keywords, *and* punctuators to be the binding, while runtime declarations can only be identifiers and keywords (depending on the context)....