Abduqodiri Qurbonzoda

Unfortunately, we are constrained by JMH capabilities. Adding an annotation that JMH does not support would require us to process the annotations within kotlinx-benchmark.

Hi, This is done intentionally. The persistent collections are also immutable, and their internal state never changes after initialization. Therefor, caching is not possible. Since `PersistentMap.values/keys/entries` returns a lightweight object,...

When considering the introduction of backing fields for the `entries`, `keys`, and `values` properties, an important factor should be taken into account. A persistent map is recreated with each mutation,...

Hi @gino-m If you added the library to the `common` source set dependencies, there is no need to add it to `js`. You should be able to use it in...

The library currently does not export any API to JS code. But the library public API should be accessible from Kotlin code in `jsMain` source set.

@gino-m There are ongoing efforts in stdlib to make this possible. See * https://youtrack.jetbrains.com/issue/KT-34995 * https://youtrack.jetbrains.com/issue/KT-44871 Is it what you are asking for?

Currently all implementations are internal, only interfaces are public. > to customize the collections to use referential equality Do you mean to treat two elements of a collection equal only...

The `Immutable` and `Persistent` interfaces were introduced to allow users implement alternative versions that better suite their use cases. For example, in projects where collections are frequently accessed but very...

Hi @daniel-jasinski, To better understand the specific use cases and motivations behind this feature request, we would greatly appreciate it if you could provide us with more details. * What...

@sgammon, thank you for your elaborate answer. We will aim to include module-info in our upcoming releases.