> it will become domain.stacked-column-chart/prepare-general-chart in use anyway. Only if you use a fully qualified namespace. If you use an alias, it might end up being the-alias/prepare-general-chart. But of course, aliases should be chosen in a way that makes it obvious what it points to. :)

The alias ends up being stacked-column-chart/prepare-general-chart in use. This use also only happens in a place specific to domain, so I have domain.subdomain1 and domain.subdomain2 in use so it's not a problem Thank you for pointing this out

I shrunk domain.subdomain1.stacked-column-chart in the original message for brevity 😅

I mean, I am guessing it is for some sort of efficient call. But what exactly makes this an optimal way of writing it?

Without explicit arities, a vararg function would have to be used. It is simply less efficient.

The function stops at 3 arguments. I am guessing that is the tipping point between it being efficient and it being ludicrous?

Though, anything with more than 3 arguments should probably be closed in a different way as opposed to invoking a partial.

Specifically an array has to made at runtime to support the varargs, I believe

> I am guessing that is the tipping point between it being efficient and it being ludicrous? That would be my guess, yes.

we have some ideas about making vararg handling more efficient that may make this unnecessary in the future (tip the balance away from unrolling)