Add @JvmStatic to generated serializer() in Companion

[cdprete]

What is your use-case and why do you need this feature?

The serializer() method that gets added/generated in a companion object of a class is not marked with @JvmStatic.
While it works with no issues in Kotlin, in Java its UX is very unpleasant since we've to do MyType.Companion.serializer() all the time.

Describe the solution you'd like

Mark the generated method with @JvmStatic so that MyType.serializer() is enough also when the library is used in a Java project.

[sandwwraith]

Java's clients are already in a weak position due to the inability to call reified serializer()/encodeToString() functions. Is there a strong demand for using kotlinx.serialization's API from Java side? What is your use-case? Spring application?

[cdprete]

Is there a strong demand for using kotlinx.serialization's API from Java side?

Not directly, but the library is in Kotlin and the Java app just uses it. From the Kotlin side, it's the only one which worked with data classes and unsigned types.

The application itself is in Spring Boot, but it doesn't really matter in my view.

Java's clients are already in a weak position due to the inability to call reified serializer()/encodeToString() functions.

True, but it still works by providing the various serializes by hand, through the method exposed from the Companion.
This is feature request wants just to allow Foo.serializer() as well as the already possible Foo.Companion.serializer().

[cdprete]

@sandwwraith is that explanation enough?

[sandwwraith]

Yes. I'm a bit concerned because we'll have a duplicated method in the bytecode, but maybe it's OK. Although we can try to solve this problem by migrating to companion blocks from new KEEP, if that's possible.