You can ask question and reply to it yourself :sli...

# coroutines

[orangy]

You can ask question and reply to it yourself 🙂 I think that explanation like this should be stored on something more durable than Slack channel with message limit…

[elizarov]

orangy: Is it really allowed on stackoverflow ?

[orangy]

yep, you need to mark it as community content or something

[orangy]

See @apatrida q&a there

[orangy]

https://stackoverflow.blog/2011/07/01/its-ok-to-ask-and-answer-your-own-questions/

[kirillrakhman]

you don't need to mark it as anything. just ask and answer https://stackoverflow.com/help/self-answer

[kirillrakhman]

it's actually encouraged but some users don't knwo that and leave negative comments or votes, that's why it can be useful to link to that page in the footnotes of your question/answer.

[thomasnield]

Why not just put it on a document on GitHub?

[elizarov]

It is harder to discover this way. Of course, I might just add another section into the design document going deeper into the dark corners of implementation, but it seems that a Q/A on stackoverflow is just a better format for that kind of explanation

[groostav]

FYI: one of the thoughts that has crossed my mind is asking questions on stack-overflow that I know are going to be asked and then copy-pasting sections of that document in as the answer because I'm a shameless stack-overflow point theif. Way better if you do it since your the authority on kotlin co-routines.