Sam Goto

> The doc identifier makes it pretty straightforward to implement as a macro. I generally the doc {}-like syntax too, but I wasn't sure how to go to code and...

> Yep: > let x = { a }; > is that a doctree or an object literal shorthand? Yep, I was a little worried about that. Note that there...

> (b) How does kotlin/groovy get away being able to parse builders? Wow, just reading more closely what Kotlin seems to be doing, it seems like the trick here is...

> Absolutely. Seems like you could just define a bunch of macros and dispatch to functions based on MacroContext#name. However, I don't know that I would create a bunch of...

from the little that i'm playing with the editor and the reference documentation, it doesn't seem like i'd be able to accomplish this with the current affordances. it seems sweet.js...

> There's also nothing in the a macro specific to a so you could make this more generic with a helper imported from another file. I think this is the...

It seems like this was introduced and then has gone away. Just checking: is it deliberate that this [documentation for the readtable](http://www.sweetjs.org/doc/main/sweet.html) is outdated? if so, is there a replacement?

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)? On a side note, what is...

Agreed on the importance of the instructions to be put up and center before other details.

I tried to compile some of these "guiding principles" but the feedback that we got was generally that there isn't enough convergence to call these "principles" more so than something...