Roger Caplan

We'd like to log essentially a stack/tree of coroutine lifecycles, e.g. ``` foo#264 created from bar#453 baz#13 created from foo#264 baz#14 created from foo#264 baz#14 ended baz#13 ended foo#264 ended...

alternatively, making `CoroutineContext.coroutineName` public would be sufficient for our current use case.

Would you accept a pr that makes `CoroutineContext.coroutineName` public (and adds docs)?

`CoroutineName` does not include the sequence number unfortunately

As a workaround, would you accept a pr that allows the caller to optionally provide their own `Dispatcher`? I'm thinking that `OkHttpClient.Builder.dispatcher`'s type could be an interface (that `Dispatcher` implements),...

thanks - to answer your earlier questions: > Are thing thinking this is a piece of metadata that is tagged with every session, and immutable throughout that session (e.g. similar...

> Would this be of interest to you if you can get this as a log associated with a cold start session? Yes, having this as a log associated with...