Hi all, what’s a good upper limit for # of paramet...

# compose

[Tash]

Hi all, what’s a good upper limit for # of parameters for a Composable (incl ones with default values)?

[Zach Klippenstein (he/him) [MOD]]

640K parameters ought to be enough for anyone

[Kirill Grouchnikov]

OutlinedTextFieldLayout has 24

[Tash]

oh 24! trying to find anything within material/foundation that has more than that…at the very least, maybe 24 is a good upper limit esp if some params are optional… 💭

[Tash]

just for context, trying to come up with a good rule of thumb for customizing detekt/static analysis rules

[jim]

Limits are meant to be broken.

[ephemient]

there's a limit of 255 parameter slots on JVM method signatures

[romainguy]

Note that when using named parameters, Kotlin will add an extra parameter per 32 parameters (+ an extra Object if I remember correctly)

[Zach Klippenstein (he/him) [MOD]]

And Compose adds its own parameters too

[romainguy]

So you can’t have 255 params in the original function declaration

[romainguy]

Yeah good point

[ephemient]

when using named parameters when using default parameters, yeah there's a bitmap int for each set of 32 parameters, and a marker parameter to prevent collisions with other overloads

[ephemient]

Compose adds 2 hidden parameters? I think that brings us to 244 usable parameters, in theory (half that if they're long or double because those take up two slots)