A modern programming language that makes developers happier.

kotlinlang

What do you want to happen? An error? Note that `typealias` and `import` are very different, `typealias` is _only_ about the type, `import` is the actual class but the classname can also happen to represent the type.

Two private type aliases in two different files should not collide as I would expect private to be limited to the file. As is the case with any other private symbol.

In the import case I would expect that `Long` continues to be available to me. I don't really understand why default imports are removed just because an aliased import is present.

Missed the private part, that's indeed a bug: <https://youtrack.jetbrains.com/issue/KT-24700>

why do you rename the import and still want to use the previous name?

I tried the import way because the private type aliases are broken. :wink: