Vsevolod Tolstopyatov

The update will arrive around 1.7.0 release

We'll provide either a workaround or will change the default behaviour in the next major version, thanks everyone for the reports!

Hi, sorry, this PR eluded me. We are very careful with time-related API and still not sure how to properly expose it (e.g. https://github.com/Kotlin/kotlinx.coroutines/pull/2745#pullrequestreview-681969186 and https://github.com/Kotlin/kotlinx.coroutines/pull/2738) We'll use this work...

Also, please change the base branch to `develop` and rebase on the latest `develop` for the sake of simplicity

I'll return to this PR during the course of next week, no worries here

Sorry for the delay with review -- caught COVID and became even less responsive :(

Thank you! 👍

We're still deciding how to proceed with active development of coroutines on JS, so this is on hold right now

Preliminary data ``` Benchmark Mode Cnt Score Error Units LookupOverheadBenchmark.dataPlain thrpt 14 9.831 ± 0.457 ops/us LookupOverheadBenchmark.dataReified thrpt 14 3.326 ± 0.084 ops/us LookupOverheadBenchmark.genericPlain thrpt 14 5.473 ± 0.565 ops/us...

The following best-case approximation of caching: ``` @Benchmark fun objectApprox(): Object { typeOf() return Json.decodeFromString(Object.serializer(), "{}") } ``` gives ``` LookupOverheadBenchmark.objectApprox thrpt 14 13.181 ± 0.821 ops/us ``` which is...