Now that Kotlin 1.9.20 will work with JVM target o...

# getting-started

[Klitos Kyriacou]

Now that Kotlin 1.9.20 will work with JVM target of 21, in which ArrayList now has a reversed() method that does what Kotlin's asReversed() does (returns a reversed view of the original collection), will this new reversed() method cause any confusion with Kotlin's existing reversed() function which returns a new List?

[ephemient]

stdlib collections extensions are supposed to have some magic so they're prioritized, this has come up before (e.g. forEach)

[ephemient]

hmm well experimentally it seems to work out for a different reason

val a: List<Any?> = ArrayList()
a.reversed() // calls Kotlin extension
(a as java.util.List<Any?>).reversed() // calls Java default method

[Klitos Kyriacou]

Similarly:

fun foo(list: ArrayList<Int>) {
    list.reversed()  // calls Kotlin extension
    if (list is SequencedCollection<*>)
        list.reversed()  // calls Java method
}

[Loney Chou]

I'd expect kotlin to have sequenced collections too. Good for unification.