Yes, when you want to use an array as carrier for the tuple. It's also consistent with the current arrays in the case of singleton tuples.
Other carriers can be considered. A kind of lightweight object could often be more suitable in the case of single tuples. That would allow accessing the members through names instead of indices. E.g.
object(int a, string b)
could be a shorthand for adding a class
class (int a, string b) {}
but with the addition of built-in support in sprintf, encode_value etc. I've often wanted something like that to make it easy to use objects as simple data carriers.
If the members of the tuple are nameless they would be accessed through numeric indices. (And yes, if "object" is used as keyword like above there'd be an ambiguity in the case of a single nameless member, so it's not ideal in that regard.)