Proposal: Allow TupleElementNames on custom types

[dotlogix]

I just discovered how named value tuples actually work behind the scenes. One idea came to my mind, would it be possible to add support for [TupleElementNames] for custom types?

For one of my projects I want to create a custom tuple like types so that I can add abstract static methods to expose additional functionality on a tuple. Unfortunately extension methods don't work for value tuples because the TRest parameter can't be type constraint to allow extension methods on this parameter itself (to allow any tuple to use the extension method).
However with static abstract interfaces this can now easily be done.

Therefore I want to create a custom struct similar to a ValueTuple with Properties Item1...Item8 + TRest but I would at least like to support to define TupleElementNames to rename them for development so that I could use a method like:

[TupleElementNames(["id", "name"])]
public MyValueTuple<int, string> GetTuple(){ ... }

This would then allow to use myTuple.id and myTuple.name. So basically the question is if this functionality could be exposed somehow so people could create their own RefTuple or other generic base types with tuple name functionality.

[colejohnson66]

Is your idea that these names would pattern match with properties/fields called Item1, Item2, etc. like the normal ValueTuple<T, ..>?

[dotlogix]

Yes.
name1 would resolve to Item1, name2 to Item2, ...
For bigger tuples (T1..T10) name8 would then resolve to Item8.Item1 and so on.

I think this is how it works for ValueTuples right? I would also be fine with a forced interface like IValueTupleLike<T1, T2, ...> to ensure compatibility with the usual name resolve mechanism if neccesary.