Splatting large collections is bad for compiler performance, so indeed it could hurt. The issue is that a collection of 100 elements being splatted into a function creates a function with 100 arguments, each with a possible distinct static type. So the type signature becomes huge.
In general, I’d use splatting sparingly: Only when you statically know the length of the splatted collection, and only when it has a handful of elements or fewer.
So, expanding the API surface for splatting could be a disservice to users, creating tempting APIs that degrade performance unexpectedly
I don’t think that would be an unexpected performance degradation, since it would be the same as max([1,2,3,4,5]...), right? it’s just letting people do what they already could with functional notation
to clarify, I’m not saying [1,2,3,4,5]... |> max is a good example; it was just the first function that came to mind