On 5/8/2020 9:36 PM, Manu wrote:
> It's still hideous though. Fundamental language features would ideally be
> acknowledged and speced rather than expressed incidentally by an ugly hack.
We can defer this discussion until the DIP is presented. But the existence of
the AliasSeq should be discussed in the DIP as an alternative.
For instance, it would be nice for a function to return a tuple:
AliasSeq!(int, float) mrv() { return AliasSeq!(1, 1.0f); }
But that doesn't really make sense from the perspective of the template arg list hack we use, relative to a proper language tuple.
Instead we use a struct named `Tuple`, which isn't a tuple, it's a struct, and it infers a lot about ABI, move/copy semantics, etc.