Static imports in Java are not “bad”. Static mutable state can cause problems. Kotlin helps one avoid mutable state, with an emphasis on immutable data and pure functions.

I heard stateful static functions are bad. What if the state is stored in an object? i.e.,

object Test {
  val list = arrayListOf("a","b","c")
}

fun testerSomething() = Test.list.joinToString()

The state in that example is still global.

so it would be bad to have

fun testerAdd() = Test.list.add("something")

i.e., for some type of manager class

Yes. In that case, the Test object is a mutable singleton.

oh I see because list should be private if it is in a class/object

I’d say that Test should be immutable.

well this would be for a manager class where I would have

fun add(stored: Something)

fun update(stored: Something)

fun remove(stored: Something)

fun get(id: String): Something?

so it would need to be mutable

Then I’d advise against making it a global singleton.

instead make the storage map private and have all those functions as part of the object?

Don’t make it an object declaration

oh so the map would not be in a class

I mean… don’t make it an object declaration. Define a class. Pass references to instances of that class around. That way, you can control the how the mutability affects different parts of the system explicitly.

ok thanks