Names conflict with Kotlin Standard Library - what to do?

GlenKPeterson / Paguro

Generic, Null-safe, Immutable Collections and Functional Transformations for the JVM

Other

312 stars 24 forks source link

Names conflict with Kotlin Standard Library - what to do? #20

Closed GlenKPeterson closed 6 years ago

GlenKPeterson commented 7 years ago

Thoughts:

Rename List, Map, and Set to something like Vector, Dictionary, and Bag. Rename corresponding interfaces Vec, Dict, Bag and StaticImports functions mutableVec, mutableDict, mutableBag.
Provide a separate version of Paguro for Kotlin. Maybe all unit tests would be written in Kotlin?
Provide a pure Kotlin version with the above changes.

GlenKPeterson commented 6 years ago

For now, if you're using Kotlin, you want the 3.1 version. Java-only, stick with 3.0. The 4.0 version looks like it will be a rewrite in Kotlin. I'm closing this because no more input is necessary.