Parameter type of addAll/putAll methods about ceylon-sdk HOT 6 CLOSED

Out of curiosity: why?

from ceylon-sdk.

For instance I'd like to be able to use addAll to add the elements of some other List or Iterable to my MutableList by writing lst1.addAll(lst2). If the parameter type is Element... then I have to write something like lst1.addAll(lst2.sequence...) or for (e in lst2) { lst1.add(e); }. On the other hand I can easily change lst1.addAll(1, 2, 3) to lst1.addAll{1, 2, 3}. So I guess parameter type Iterable is preferable here.

from ceylon-sdk.

Ok understood... although this makes me wonder if this is not something you want in most cases anyway. I mean what's the advantage of having variadic parameters now? Are there examples where you'd want them where passing an Iterable or List just doesn't make sense?

from ceylon-sdk.

Citing from @gavinking's comment ceylon/ceylon-spec#488 (comment) :

Sequenced parameters are now a much more special-purpose thing for cases where you don't expect to ever be receiving collections. Things like log(), format(), assertTrue(), etc.

from ceylon-sdk.

FTR there's a further (slightly obscure) case where sequenced parameters are useful: when you want to write a single method that can masquerade as a T(X), T(X,X), T(X,X,X), etc. This is a bit like JavaScript's arguments array.

I think this will turn out to be very nice for some metaprogramming scenarios. For example, it seems to be a nice way to write interceptors.

from ceylon-sdk.

Done.

from ceylon-sdk.