On Thu, Nov 27, 2014 at 6:53 PM, Janko Thyson janko.thy...@gmail.com
wrote:
Well, the benefit lies in the ability to pass along arguments via `...` to
more than one recipient that use *identical argument names* and/or when
these recipients are not necessarily located on the same calling stack
Janko,
I'm not entirely sure I understand your proposal. Are you suggesting
methods be dispatched based on the *contents* of ... (ie which arguments
are in there)? This seems like it would be pretty different from how
dispatch behaves now, which is entirely class based.
Even the dispatching
Hi Gabriel,
and thanks for answering. I'm basically just trying to find a way to use
the power of `...` in more complex scenarios and I'm well aware that this
might not be the best approach ;-)
Regarding your actual question:
Are you suggesting methods be dispatched based on the *contents* of
I think I understand what you're saying now, but I'm still kind of missing
the benefit from the approach.
As far as I can tell just giving foo formals for the arguments you want it
to catch gives you the end result you want, doesn't it?
And if the generic has ... in it, you can (if you're very
Well, the benefit lies in the ability to pass along arguments via `...` to
more than one recipient that use *identical argument names* and/or when
these recipients are not necessarily located on the same calling stack
layer.
I'm *not* after a *general* change in the way arguments are
