Leonid Startsev

Hi, maintainer of kotlinx.serialization here. We've changed annotation retention to binary because we were not expecting that anyone would read them via reflection (the kotlinx.serialization itself reads them via compiler...

@gildor Serialization plugin generates code which is abstract over a storage; one may write the implementation of `CompositeEncoder` which write primitives to a `Parcel` and therefore make all `@Serializable` classes...

@gildor > you cannot use such class without Parcelable implementation as a property of another parcelable class Is this necessary for interop with some existing Android APIs? Because that should...

@soywiz I think that approach with 'global map' is quite ad-hoc and for different message types, you probably want to use a polymorphic serialization, discussed in the 'appendix' section. There...

@pdvrieze Idea behind this is while optionality is an attribute of a property solely inside the structure, nullability is an attribute of an unbound type (use-site, indeed). A particular serializer...

@dhakehurst I agree that modern programmers don't want to think about 'by-value' or 'by-reference' and they shouldn't think about it – thanks to the GC which can collect cycles and...

@arkanovicz This KEEP should match the 1.0 implementation of kotlinx.serialization framework. Can you spot any contradictions?

The problem is in `KClass` that requires T to be non-nullable and inferred in this overload automatically. However, I think it may be possible to change the signature of `contextual(kClass:...

Sorry, I don't get your question. Are you experiencing problems with `call.respond()`? This is function from ktor, not from kotlinx.serialization. Better ask them then.

I'm not sure it's possible to control the obfuscation pattern on our side, but we'll check if there are any specific rules. `javaClass.simpleName` unfortunately is not an option because the...