Name overrides are one thing, and you could provide a generic

@TargetName

annotation for that. I'm referring more to also exposing things like @JvmField, @JvmStatic, @JvmOverloads, etc. Why do those belong in common code?

For example, say I have the following in a common module:

fun List<Vector2>.bounds() = ...
fun List<Vector3>.bounds() = ...

Kotlin can handle those two functions just fine, but they cannot be statically resolved on the JVM, so I want them to be renamed (only on the JVM) to

bounds2d()

and

bounds3d()

. How would I do that if I can't use the annotation in common code?

• Define these in the platform modules instead • Wait for the JVM to support reified generics • Name-mangling

Things like annotations for annotation processing keep it concise without need to essentially duplicate a class accross android and jvm implementation too

@eddie That would add a severe degree of complexity if you ask me. If they are pure Kotlin code defined in a common module, it would be a pain to have to maintain them in multiple modules purely for the sake of naming, when you're not really changing the implementation at all.