On 07.03.2018 18:23, Jonathan M Davis wrote:
However, even doing something like

auto func2(Parameters!func args = AliasSeq!(1, 2, 3))
      return func(args);

doesn't work properly. If that version of the function is used, then the
call which passes all three arguments compiles, but the others don't, which
means that it's acting like the AliasSeq isn't even there (though it's
clearly doing_something_  with it, since you get a compilation error if one
of its values is void). I'd argue that either the values in the AliasSeq
should be being assigned, or they shouldn't be legal. Having them be there
but ignored just plain seems like a bug, but I have no idea what the
compiler is thinking here.


Reply via email to