Fabio Labella

@satorg that doesn't make sense to me, you've just described how a non-memoized Resource would behave. Think about this: what happens if I call `memRes.use` twice inside that `memoize(res).flatMap {...

In terms of api expressiveness, you might also want to look at https://systemfw.org/dynosaur/#/schema the library was originally inspired by xenomorph as well, but it ended up making different tradeoffs

Async exceptions needn't (and shouldn't) appear as Exception, only IO, because catching them requires a special operation that isn't Exception.catch

A relevant discussion popped up on Discord, copying it here because I think there is useful insight. ---- @SystemFw: Since this discussion pops up periodically, here's your periodic reminder that...

that `EntityEncoder` should not be defined like that. I don't know if it's related to this specific problem or not (probably not), but it might be worth having a look...

The puzzling thing here is the interaction with partial unification. I have it seen it happen e.g. wrt order of type parameters, but never sub typing constraints

Perhaps someone can open a PR to the `rho` docs for this?

> it seems like it should have to reraise the failure The correct protocol for interruption is to clean resources and rethrow, never swallow a ThreadKilled. However, when I did...

> I don't know if there is really a better option. fork only accepts {IO}, not Exception, and anything that bubbles up to the top of the fork is ultimately...

Generally speaking I'm queasy on `*Local` because of this type of issues, but also queasy on the alternative (tagless + Kleisli) because it raises the complexity floor so high for...