and if it somehow does become a problem, congratulations! you are facebook and rolling in money and ...

# android

[jw]

and if it somehow does become a problem, congratulations! you are facebook and rolling in money and you can retire and hire 300 other Android devs to fix the problem and go live on your private island

[gildor]

@adam-mcneilly just for fun grep unpacked Facebook APK and found 74 enum declarations 😬

[jw]

I suspect they aggressively optimize them out. At Google we have something called @SimpleEnum which requires that the enum can be optimized into an int and fails the build if it can't.

[gildor]

Is that optimized by proguard/r8?

[jw]

Yes

[gildor]

So is it just enum without fields and methods marked as SimpleEnum?

[jw]

Yes. The key is just that you are prevented from causing de-optimization without explicitly removing the annotation.

[gildor]

Such approach is much better than @IntDef imo
Thanks for information

[jw]

I don't disagree!

[louiscad]

@jw How can I use @SimpleEnum in my projects? Does proguard/r8 handle inlining them to int even when there are extension functions/properties for the enum?

[jw]

You cannot. Extensions are static methods so they don't affect the enum.

[jw]

Just write normal enums. 90% of them will optimize away anyway and you don't have to care.