Kotlin: listOf() versus emptyList()

So I noticed that Kotlin tends to have several ways of doing the same thing¹. Sometimes these are actually identical, sometimes there are subtle differences.

That makes things hard for me.

Let's take this trivial example.

There is no difference. The one thing you could mention is that emptyList() more accurately conveys what you are trying to do.

There's something similar in Java. Collections.emptyList() versus List.of(). The comments on [2] seems to be very interesting.

In Java one could argue that List.of() is new, so should be used. And we could assume that the Language Architects in Java wouldn't add a List.of() for no reason.

References

[1] Kotlinlanguage Reference - emptyList

https://kotlinlang.org/api/core/kotlin-stdlib/kotlin.collections/empty-list.html

[2] StackOverflow - List.of() or Collections.emptyList()

https://stackoverflow.com/questions/39400238/list-of-or-collections-emptylist

Java - Behaviour of Equals in Collections

I just thought I'd write some things down that I already know, but sometimes it's nice to see this proven.

It's a very very beginner Java subject, but people won't fault me for blogging about it.

It might be of some use to somebody.