Tim Williams

That's awesome! I'd be more than happy for extra contributors! If anything isn't clear and needs some explanation, let me know and I'll try to help.

I really like this idea. The key benefit I think, is that the set of choices given for case analysis are just a record of functions (or an arbitrary expression...

It's a missing feature in Expresso, but not a feature that I think is needed for the configuration use cases I had in mind. I do have an idea on...

Yes a fixed-point combinator could work, but type-level functions would be a costly addition. The type-synonyms are lazily expanded, so it may also be possible to use a simple inductive...

Records definitely subsume tuples, that said, I agree that writing "{ fst = x, snd = y }" is much more noisy than "(x, y)". Perhaps a reasonable solution is...

Hi Hans, The lazy tests are misnamed, they are really non-strictness tests. Laziness is of course difficult to test as it's a performance optimisation. The idea is that the second...

Hi Hans, I'm still not sure the evaluator is working correctly with respect to laziness: e.g. :peek { x = fib 300 } seems to hang as if the fib...

Apologies for the late reply. You are absolutely correct that the implementation here does not use full qualified types. That is really part of the point of this code, to...