gilch

These infinite loops are supposed to happen so rarely that if there are a multiple worker JVMs in subprocesses, occassionally killing and restarting one shouldn't affect run times much. I...

This seems to have been closed without a fix. My workaround config is working for me, so I have not been paying attention, but it's still a poor user experience...

This actually seems a bit more difficult than I first thought. We're relying on Python's parser in bracketed expressions, but the macro character ! probably shouldn't be valid inside of...

F-strings though. We'd want to be able to turn the macro back on in those.

As convenient as this would be, it kind of doesn't seem worth it. The thing I miss the most in bracketed expressions so far is the module literals. It would...

Given f-strings, `!` isn't a good macro character choice, because it does have meaning there. `;` might be the best option. I'm pretty sure it's not in format specifiers. Normally,...

A macro like this wouldn't be too hard to write: ``` !where: (spam+eggs) spam macro:spam eggs macro:eggs ``` It feels more compact than the `!let` anyway. It could also be...

A tutorial in the style of [learn X in Y minutes](https://learnxinyminutes.com/docs/python3/) might also be good. Especially if we can doctest a REPL session. I also really like the organization of...

`!where` from #59 is a possibility. Hissp has more bundled macros now. Hebigo ought to be at least as capable (except, perhaps, for the reader macros). Nothing is really stopping...

I'm wondering if this would help readability at all for a complex let destructure. I'd have to see it.