kotlin-tooling-immutable-collections-0-5-x-migration

Migrate Kotlin immutable collections to 0.5.x by renaming copy-returning methods to their participial forms. This automated refactoring targets PersistentList, PersistentMap, and PersistentSet interfaces to resolve deprecation warnings.

KEEP-0459 is the Kotlin evolution proposal that requires renaming copy-returning methods in kotlinx.collections.immutable from the 0.3.x/0.4.x naming convention to the 0.5.x participial form. It enforces binary compatibility across persistent collection interfaces.

Yes, refactoring persistent collections requires a functional build environment. The migration leverages existing compiler deprecation warnings to accurately identify and safely rename specific call sites without destructive changes.

Yes, you can migrate custom classes implementing PersistentCollection interfaces. The migration provides specific guidance and refactoring patterns for updating custom implementers to align with the 0.5.x participial method naming convention.

Your Kotlin build fails after upgrading kotlinx.collections.immutable because 0.5.x deprecates older copy-returning method names. You must rename these methods to their participial forms to restore compilation and ensure binary compatibility.

The best way to resolve deprecation warnings for PersistentList and PersistentMap is compiler-driven migration, which leverages build output to accurately identify and rename deprecated call sites to their 0.5.x participial forms.