Kotlin/kotlinx.collections.immutable issues and pull requests

#126 - Please cache the hashCode

Issue - State: closed - Opened by zajac over 2 years ago - 2 comments

#126 - Please cache the hashCode

Issue - State: closed - Opened by zajac over 2 years ago - 2 comments

#126 - Please cache the hashCode

Issue - State: closed - Opened by zajac over 2 years ago - 2 comments

#125 - Questionable PersistentList time complexity specification

Issue - State: open - Opened by mcpiroman over 2 years ago - 2 comments
Labels: doc

#124 - Update readme and changelog

Pull Request - State: closed - Opened by qurbonzoda over 2 years ago

#124 - Update readme and changelog

Pull Request - State: closed - Opened by qurbonzoda over 2 years ago

#124 - Update readme and changelog

Pull Request - State: closed - Opened by qurbonzoda over 2 years ago

#123 - Consider adding filterTo, mapTo, etc overloads

Issue - State: open - Opened by belyaev-mikhail over 2 years ago - 3 comments

#123 - Consider adding filterTo, mapTo, etc overloads

Issue - State: open - Opened by belyaev-mikhail over 2 years ago - 3 comments

#123 - Consider adding filterTo, mapTo, etc overloads

Issue - State: open - Opened by belyaev-mikhail over 2 years ago - 3 comments

#122 - Documentation issue ?

Issue - State: closed - Opened by vgodara almost 3 years ago - 1 comment

#122 - Documentation issue ?

Issue - State: closed - Opened by vgodara almost 3 years ago - 1 comment

#122 - Documentation issue ?

Issue - State: closed - Opened by vgodara almost 3 years ago - 1 comment

#122 - Documentation issue ?

Issue - State: closed - Opened by vgodara almost 3 years ago - 1 comment

#122 - Documentation issue ?

Issue - State: closed - Opened by vgodara almost 3 years ago - 1 comment

#121 - Upgrade Kotlin to 1.6.0 and add more K/N targets

Pull Request - State: closed - Opened by qurbonzoda almost 3 years ago

#121 - Upgrade Kotlin to 1.6.0 and add more K/N targets

Pull Request - State: closed - Opened by qurbonzoda almost 3 years ago

#121 - Upgrade Kotlin to 1.6.0 and add more K/N targets

Pull Request - State: closed - Opened by qurbonzoda almost 3 years ago

#121 - Upgrade Kotlin to 1.6.0 and add more K/N targets

Pull Request - State: closed - Opened by qurbonzoda almost 3 years ago

#120 - production-ready? or, roadmap?

Issue - State: open - Opened by cprice404 almost 3 years ago - 5 comments

#120 - production-ready? or, roadmap?

Issue - State: open - Opened by cprice404 almost 3 years ago - 7 comments

#120 - production-ready? or, roadmap?

Issue - State: open - Opened by cprice404 almost 3 years ago - 5 comments

#120 - production-ready? or, roadmap?

Issue - State: open - Opened by cprice404 almost 3 years ago - 5 comments

#120 - production-ready? or, roadmap?

Issue - State: open - Opened by cprice404 almost 3 years ago - 7 comments

#119 - Update to Kotlin 1.5.31

Pull Request - State: closed - Opened by ansman about 3 years ago - 5 comments

#119 - Update to Kotlin 1.5.31

Pull Request - State: closed - Opened by ansman about 3 years ago - 5 comments

#118 - Support for M1 simulators

Issue - State: closed - Opened by karelp about 3 years ago - 2 comments

#118 - Support for M1 simulators

Issue - State: closed - Opened by karelp about 3 years ago - 2 comments

#117 - jvm: add footprint benchmark via JOL

Issue - State: open - Opened by vlsi about 3 years ago - 1 comment
Labels: doc

#117 - jvm: add footprint benchmark via JOL

Issue - State: open - Opened by vlsi about 3 years ago

#117 - jvm: add footprint benchmark via JOL

Issue - State: open - Opened by vlsi about 3 years ago

#117 - jvm: add footprint benchmark via JOL

Issue - State: open - Opened by vlsi about 3 years ago - 1 comment
Labels: doc

#117 - jvm: add footprint benchmark via JOL

Issue - State: open - Opened by vlsi about 3 years ago

#117 - jvm: add footprint benchmark via JOL

Issue - State: open - Opened by vlsi about 3 years ago

#117 - jvm: add footprint benchmark via JOL

Issue - State: open - Opened by vlsi about 3 years ago

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#116 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results #114

Pull Request - State: closed - Opened by qurbonzoda about 3 years ago - 2 comments

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#115 - Candidate fix for #114

Pull Request - State: closed - Opened by chuckjaz about 3 years ago - 1 comment

#114 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results.

Issue - State: closed - Opened by chuckjaz about 3 years ago - 8 comments

#114 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results.

Issue - State: closed - Opened by chuckjaz about 3 years ago - 8 comments

#114 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results.

Issue - State: closed - Opened by chuckjaz about 3 years ago - 8 comments

#114 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results.

Issue - State: closed - Opened by chuckjaz about 3 years ago - 8 comments

#114 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results.

Issue - State: closed - Opened by chuckjaz about 3 years ago - 8 comments

#114 - PeristentHashMapBuilder.putAll() with another persistent hash map can produce incorrect results.

Issue - State: closed - Opened by chuckjaz about 3 years ago - 8 comments