Youssef Shoaib

Thanks for having a look at this! This is plenty useful! A lot of the examples I have in mind would gain a few extra `CapSet`s passed around, which is...

FWIW, the compiler already accepts this: ```effekt effect Foo[C]: Unit def bar{this: Region}: Unit / Foo[=> Unit at this] = do Foo[=> Unit at this] ``` but, it's very unhappy...

FWIW I've minimized the example further. Hope that helps!

I keep running into this randomly. Will try with `--no-optimize`, but it's annoying since optimizations are useful to showcase sometimes, but alas. EDIT: It thankfully works with `--no-optimize`, and compilation...

Converted to a draft temporarily until we add `context` bridges for `Resource` and `Saga`

Oops didn't even notice the `val` thing. I sometimes wish the compiler would continue accumulating errors, instead of (seemingly) just stopping on the first one, but ik that's a hard...

> though only for those with annotated return types FWIW, Kotlin resolves this by having 2 phases: one where it checks only declarations with implicit return types, and one where...

> > We might need to update the parts that mention unboxing, since there is no syntax anymore Note that #1172 added back the explicit syntax.

The tests prefixed with `tryCatchRecoverRaiseWithNel` are the ones where behaviour changes. I'll focus on one of them: ```kotlin @Test fun tryCatchRecoverRaiseWithNel() = runTest { accumulate(::merge) { try { withNel {...

I'm pretty sure now it's not a miscompilation. I'm preparing a small reproducer, but basically the type of `resume` (when there's bidirectional effects, or the effect takes in a computation...