A modern programming language that makes developers happier.

kotlinlang

Running suspend function in `finally`  block … _foot marksmanship_ or not? :thinking_face:

(Or put another way, is it a bad idea to run a suspend function in the finally block? Use case is I don’t want to catch errors from `suspendFunA()` but I need to cleanup resources used &amp; reset a lock within `suspendFunB()`)
```   try {
~    suspendFunA()
   } finally {
~    suspendFunB()
   }```

The foot-gun is when the coroutine was cancelled. In that case, `suspendFunB()` will just fail again as soon as it tries to suspend. To fix it:
```try {
  suspendFunA()
} finally {
  withContext(NonCancellable) {
    suspendFunB()
  } 
}```

Arrow has a `Resource` datatype that does exactly this (with `NonCancellable`) so I would say yes this is the way to go. You might wanna use their `ResourceScope` abstraction if you're doing this a lot