Nested classes in ProtoBuf produce empty array for native release binary about kotlinx.serialization HOT 5 CLOSED

Thanks for report. It happens for me for both linuxX64ReleaseTest on Linux machine and macosArm64ReleaseTest on Apple Silicon machine. Looks like the Native issue though.

from kotlinx.serialization.

Closed in favor of https://youtrack.jetbrains.com/issue/KT-67218/Native-nested-classes-in-kx.serialization-ProtoBuf-produce-empty-array-for-release-binary

from kotlinx.serialization.

just in case: does it make sense additionally run tests in RELEASE mode (and possibly in other kotlinx.* libraries), to be proactive with such bugs?
If you think it could be useful, I'm ready to provide PR.

from kotlinx.serialization.

Yes, it makes sense. I'll ask Native team additionally of the best way to do so. We are now refactoring our build scripts (#2654), so you'll have to wait with your PR a little bit :)

from kotlinx.serialization.

okay! Thanks, I will wait for #2654.
At my side I have the following build setup for runnings native tests in release mode. (BTW, this is how I've found this issue)
Created tasks will look like macosArm64ReleaseTest in addition to macosArm64Test (same for other targets) and will be automatically registered to run on check/allTests (I haven't looked on TC setup, so not sure what is needed there).

from kotlinx.serialization.