Phil Hagelberg

I have a fix for this, but it breaks some of the tests: https://git.sr.ht/~technomancy/fennel/commit/4f192a50bb94011ffea28c1c1e114e687d0c9186 ```fennel (and (values)) => was true, becomes nil (and true true (values)) => was true, becomes...

> It would certainly be possible to extend the special-casing detection It's easy to detect a *direct* call to `values` inside an `and`/`or`: ```fennel (if (and (or (= :or name)...

> just a thought — maybe we can splice values into current form unless they're in return position? That's basically what happens today; we compile the final argument to `and`/`or`,...

Right before the line you listed, you can see it declares `local root`. So that code does not in fact make any changes to the global environment. Perhaps the error...

Might cut a release soon, so if you have any info to share about this problem, now would be good.

I love this idea, thanks for bringing it up. I think it's a great idea to allow plugins to track dependencies between modules and the macros they load. > I...

> there wasn't an explicit hooks test that I could see Try grepping the test dir for `plugins` and you'll see a few tests we have for this already. >...

This is probably the longest-standing annoyance in the entire Fennel compiler. I've tried to fix it multiple times but it's a lot more subtle than it looks. But I would...

To clarify, the difficulty is that the compiler has a fairly deep-seated assumption that all expressions are just single strings and that larger chunks of code consist solely of statements....

Is this the same problem as https://todo.sr.ht/~technomancy/fennel/57 ?