Abduqodiri Qurbonzoda

Thank for your feedback! A similar issue is discussed here: https://github.com/Kotlin/kotlinx.collections.immutable/issues/8 We are aware of the possible confusion, but we have not yet found a satisfactory naming scheme. In the...

Hi, Thanks for reporting the issue. The library does not prioritise correct handling of concurrent collections. So it becomes the user responsibility to make sure the `elements` collection consistency. It...

Related issue: https://github.com/Kotlin/kotlinx-benchmark/issues/81.

> Note: This is a phase-1 implementation, with just the basic idea laid out. I would appreciate it if you could clarify what exactly you think should be included in...

There is an ongoing effort from the Build Tools team to resolve this issue: https://youtrack.jetbrains.com/issue/KT-66764

Hi, Currently, there is no support for running a specific benchmark from IntelliJ (like a unit test). However, we are working on improving documentation, especially about benchmark tasks. Please stay...

Hi, Since your report, we have significantly improved our documentation. Specifically, we have added a [separate guide](https://github.com/Kotlin/kotlinx-benchmark/blob/master/docs/tasks-overview.md) describing the Gradle tasks created by our plugin, including those used for running...

Hi @lppedd Thanks for the feedback! We will try to fix the issues ASAP.

I also can’t see any benefits of testing with different JMH versions, and I doubt it was intended to allow the use of different JMH versions. As a first step,...

> Everyone can specify their own favourite version of JMH manually, but it would be nice to have a more recent version by default. I support the idea. Given that...