effectfully

I'm going to claim that: 1. this appears to be a low priority issue 2. it doesn't seem like we definitely have a "won't do" here Hence I'm adding the...

@colll78 I do also like the idea of adding `let` to the language. Not sure if it's worth adding multi-lets, given that it's probably even more indirections than just iterating...

I've spent some time thinking about it and I believe we should definitely try adding `let` to UPLC and optimize applied lambdas to iterated `let`s (I don't think multi-`let`s would...

If we don't add a `let` (which I think we should), then we should at least consider rendering applied lambdas as lets. Currently we pretty-print applied lambdas as: ``` (\x1...

@colll78 thank you for the reference. I'm particularly glad that others do this, because we've had some debates internally whether it's weird or not to render applied lambdas as lets....

We're moving tickets from Jira, so here's some context that we had there (written by me, so biased in favor of adding `let`s) but not here: > A human thinks...

> I would expect traces to stay in the program unless I configure the compiler to remove them. Me too. We've run into this issue internally as well and we're...

We've discussed this issue internally and we agree that this behavior is pretty much a bug. We're going to fix it soon.

@zliu41 do you happen to know what the status of this issue is?

In the first place this library is an investigation of how practical descriptions (as seen in [The Gentle Art of Levitation](https://jmchapman.github.io/papers/levitation.pdf) and elsewhere) are. For your example to type check...