Leonid Startsev

This is still a big semantic change that can break someone's code, unfortunately. I think you can always specify the serializer explicitly in `encodeToString` if you want.

Hi, thanks for the report! Unfortunately, I wasn't able to reproduce the issue on a sample project. Maybe it's caused by the fact that different files in the project were...

If you want to examine bytecode, your best bet is to open compiled classfile and decompile it to Java (using e.g. built-in IntelliJ decompiler)

That's an interesting result. Maybe it is due to the fact that annotation's parameter defaults can be analyzed from a different module? (Given the expect/actual situation). To watch decompiled code,...

I think it should be easy to add such a function. Can you tell a bit more about use-case?

Note you can do this manually, e.g. ``` when(thisClass) { is List::class -> ListSerializer(myArgsSerializer[0]) is Map::class -> // etc.... } ``` But in general case, yes, such function is required

Makes sense. It seems that you altered example files, can you run `./gradlew knit` (https://github.com/Kotlin/kotlinx.serialization/blob/master/CONTRIBUTING.md#running-the-knit-tool) to re-generate documentation tests and commit the result?

So basically you want something like that, right? `val myNewSerializer = SealedClassSerializer(sealedSerializer1.sealedSubclasses + sealedSerializer2.sealedSubclasses)` for combining two sealed hierarchies. It sounds quite reasonable since we have an API to combine...

The root of the problem is that `PolymorphicSerializer` was created in a such way that objects written by him are intended to be easily restored in statically typed language. So,...

External automatic serializers generation is in many ways experimental feature for now, and due to its complexity, it has many bugs beside this one. I'll take a look at it,...