Simon Vergauwen

> Hi @davydes , it's a normal behavior as the whole runBlocking scope is interrupted when the exception is thrown. Please read more about exceptions and coroutines [here](https://kotlinlang.org/docs/reference/coroutines/exception-handling.html) or [here](https://medium.com/androiddevelopers/exceptions-in-coroutines-ce8da1ec060c)...

> because it cancels the parent in case of an unhandled exception. The exceptions is handled in both the original and my example, so it should not have cancelled the...

@j30ng thank you for the example. To rephrase my original comment, and I think I'm still in line with the original bug report. Semantically it still doesn't seem sense to...

Hey @victorhearnyeates, Thank you for your feedback. The replacement code in `ReplaceWith` is sadly not as good as we've hoped, and is in my opinion not really a good comparison....

Hey @objektwerks, We have that planned but in a slightly different way. Most code snippets are backed by KotlinX Knit, which generates actual Kotlin files which can be linked. That...

I am unsure about this addition. My immediate thoughts are that _early returning_ is considered a code-smell by many, and I am not sure what additional patterns this enables? If...

Okay, thank you for clarifying. > Perhaps it is too much a matter of style that only individual users should decide on introducing it themselves, though, but I'll leave that...

Hey @postfixNotation, I think there are a couple of things we can do, but not sure which is the best one 🤔 It also depends a bit on your use-case....

Hey @postfixNotation, > Is there an estimation of how long this might take? There is only a couple of maintainers, and sadly this is on none of our priority list....

Hey @PavlosTze, Thanks for the bug report! First of all, let's see if we can fix your snippets (for documentation purposes) In the first snippet, it's would need an additional...