System.ValueTuple isn't mentioned anywhere else in this file. Shouldn't we be a bit more specific? There are wrinkles in how tuples map to the ValueTuple types. For instance, a tuple type(T1, T2, T3, T4, T5, T6, T7, T8) must be represented as nested ValueTuples, because the TRest type argument of a tuple must always itself be a nested tuple:ValueTuple<T1, T2, T3, T4, T5, T6, T7, ValueTuple<T8>>

I see that conversions.md does mentionValueTuple<...> a few times, but it doesn't explain the required recursive encoding.

I vaguely remember that we discussed how far we needed to go with that encoding aspect.

If we can avoid referring toValueTuple<...> in this section, it's likely to make our lives easier... even if it means doing a bit more work in 8.3.11 to effectively make that theonly place that needs to go into that detail. If we can say "logically there's a type with N fields" then we can make this line (in expressions.md) simpler.

Why do we mention tuple expressions here, but we don't mention other kinds of expressions such as object creation expressions, array creation expressions, lambda expressions, and so on?

I think I'm following, but just checking.Is there a tuple typeS for every tuple expression? For instance, does(default, default) have a tuple typeS in:

(object,object)x=(default,default);