Mention that the copied exception's message must be like the original

[adamschoenemann]

Just a quick fly-by PR as a suggestion on including this information.

[elizarov]

I am not sure such a strong wording is really needed. Nothing is going to break inside coroutines machinery is the copied exception message is different from the original, so an emphasis on "must" does not seem to be warranted here. I think it is better to rephrase it as a recommendation.

[adamschoenemann]

I'm not married to the wording at all here.
But the point I wanted to come across was that it's not gonna attempt to restore the stack if the message is not the same as copied exception.
As per this line

kotlinx.coroutines/kotlinx-coroutines-core/jvm/src/internal/StackTraceRecovery.kt

Line 70 in d7de5f5

// Verify that the new exception has the same message as the original one (bail out if not, see #1631)

[elizarov]

Good point. That should be added to the docs. That is, the explanation should mentation that the same message is a prerequisite for the stack recovery mechanism.

[adamschoenemann]

Exactly :)

[adamschoenemann]

Should I close this MR and open an issue instead or what would you prefer?

[elizarov]

It just needs a bit rephrasing and clarification on why the same message is needed. No need to close PR. It can be amended.

[qwwdfsad]

Thanks! This PR triggered me to investigate the exception message comparison and uncovered #2749.

This PR is superseded by #2749