Carl Mäsak

I think the option to _edit the expression that failed_ (usually a call) would go a long way.

> 2. The REPL can import the same module multiple times, with changes in-between. If the first time the module gets imported, it has a function `rectangle` (from the example...

I've concluded that _errors are stronger than `after` semantics_, meaning that an error doesn't unwind the stack, it abruptly aborts the evaluation. Which is good news for this issue, because...

> Just doing some drive-by-commenting here: Bel is fundamentally a very interpreted/dynamic language, and modules are a feature that reaches towards the compiled/static end of things. Not that they clash,...

This issue is turning into a general request for debugging, and as such I would like to link to this paper: https://arxiv.org/pdf/1905.06545.pdf "Direct Interpretation of Functional Programs for Debugging"

Something quite close to the idea of pods seems to come up in [Motoko](https://internetcomputer.org/docs/current/motoko/main/motoko/)'s idea of **canisters**. These are actor-like persistent compilation units communicating with the outside world via asynchronous...

> Consider [the change I needed to make here](https://github.com/masak/taocp/pull/21/commits/97745f46cc957f27445975392fcc499d1e2bec04) to (the call to) the `make` macro. I don't remember exactly how it failed, or how I realized that `make` was...

> * I have no idea, going in, which function or macro emits the `'underargs` error. Cutting right to the chase, it's a little anonymous pair-producing function inside the `make`...

The correct way to think about it is probably some backwards reasoning, "here's a function signature; what would it take for that one to fail to bind? oh, it's part...

Interestingly, `hug` is used in a number of other places, and _usually_ in such a way that the "trailing one-element list element" phenomenon doesn't cause an error: * In `with`,...