Vsevolod Tolstopyatov

@sandwwraith could you please fix the example from the guide as well?

I'd say that this particular issue can be addressed with `ConcurrentLinkedQueue` + atomic around char array sizes (of course, with the loss of strictness around `MAX_CHARS_IN_POOL`)

>It almost screams for having something in the metadata of packages to allow automatic (compiler) plugin applications. This one we rather generally prohibit. Having an implicitly-enabled compiler plugin from arbitrary...

The idea behind the auto-enabled plugin is that it is enabled *by default*, and knows nothing about whether the project has any specific dependencies. What we can do to further...

@fzhinkin while you are at it, please take a look at https://github.com/Kotlin/binary-compatibility-validator/issues/73 and at https://youtrack.jetbrains.com/issue/KT-51073. It seems like they have the same (or very similar) root cause, it may save...

Could you please provide a rationale and the reasoning for the proposed API? What are practical use-cases?

`Mutable*` is another side of the story -- we could do that, and it would probably be a reasonable thing to do (after a rehearsal of our design notes regarding...

That would be a nice idea if we were just to (re-)introduce `run-blocking`. The problem is, it exists for quite a few years already, is *really* widespread (i.e. single DuckDuckGo...

One thing that is worth tweaking around is the interaction between the new and old API. I.e. right now nothing prevents users from writing something like this: ``` try {...

Note to self: revisit https://github.com/Kotlin/kotlinx.coroutines/issues/3716 when moving forward