<@U2X0FMBS9> Are you planning to support all the c...

# android

[mg6maciej]

@vyacheslav.gerasimov Are you planning to support all the cases?

[vyacheslav.gerasimov]

Yes, what cases would you like to be supported?

[mg6maciej]

It was a trick question 😉

[mg6maciej]

Supporting all basic types is not simple.

[mg6maciej]

Take a look at what generated code could like like for `LinkedHashMap<char[][], List<TreeSet<Bundle>>>`:

https://github.com/mg6maciej/hrisey/blob/develop/test/transform/resource/after-delombok/ParcelableUberComplexUselessType.java

[mg6maciej]

For a more descriptive way of showing what I consider basic types, you may take a look here: https://github.com/mg6maciej/hrisey/wiki/Parcelable#details

[mg6maciej]

And even there is a difference in generated code when field's type is final Parcelable compared to when it is not. Basically you can avoid parceling class name FQCN and when reading avoid using Class.forName and friends (talking about what happens internally in Parcel class).

[vyacheslav.gerasimov]

generated code for LinkedHashMap<char[][], List<TreeSet<Bundle>>> looks scary to me, i think first version will not handle complex types, such as collection of collection

[vyacheslav.gerasimov]

thanks for info

[mg6maciej]

Yes, it looks scary. I would never use such structure in my own code. And even if I did I would never handwrite code like this.

[mg6maciej]

It is code generated by Lombok, so user never sees it.

[mg6maciej]

But it is the most optimal way of parcelling stuff at the same time.

[mg6maciej]

Generally trying to avoid hard limit of 1MB serialized data and even trying to make sure it's as low as possible (you may see UI lags after 100kB).

[mg6maciej]

@vyacheslav.gerasimov Just noticed there was a plugin for that https://github.com/nekocode/android-parcelable-intellij-plugin-kotlin