I can think of plenty real world usecases. Take for example a network interface that can send or receive predefined packet structs. Imagine each packet require

I can think of plenty real world usecases. Take for example a network interface that can send or receive predefined packet structs. Imagine each packet requires a size header. When you want to send multiple packets at once, you now want to optimize that and only write a single initial header to the interface, preceding the data. With variadic generics, you can enable a syntax like `interface.write_packets(packet1, packet2, packet3, /* ... */);` which writes the packets in the desired optimized way. It can internally construct a serializable data tuple from the variadic generics and add the correct header only to the beginning. Without variadic generics a similar syntax is only possible with macros, which means that it cannot be implemented as a reusable trait. > It would seem to me, you're just skipping the part where you give your tuple a name, but is that even a good idea to do? Sometimes you explicitly don't want to require naming the tuple for flexibility, like in the example above.