porcuquine

Slot allocation needs to follow all the paths. It should definitely be finite. Can't you effectively inline all the funcs? The 'right' answer is probably to get this hooked up...

Yeah, maybe so.

Although I know sorting through these mechanics is tedious, having this in place will be a big step forward. Given how performance-sensitive we are, and how many interacting systems can...

I would define it to the first argument is not evaluated and must be a literal.

Cost-wise this will make it a unop. You can create a unop continuation that captures the first tag, discards the value (or not) and then expects the evaluation on the...

That was implicit in the description and examples above, but I should have mentioned it explicitly.

Not really. You can think of it ad currying/partial-evaluation. Your example is good, since CL has a function `1+`.

In any case, there would be no ambiguity. The behavior would be defined.

Oh, if you’re just wordsmithing your name suggestion then I agree. That was the original same-type? idea. Now that we’ve gone around the block, I think `same-type-as` might be the...

In this theory, we would need to provide a literal syntax for functions. If we did, that would usually be preferable (cheaper) for users, when they don't require closures. (The...