We should consider supporting expressions with tuples in expression tree lambdas.
It can be done either by
1) Introducing new nodes that represent tuple creation/conversion/field accesses or
2) Use lowered form
Option 1 is more desirable since it is more expressive, but will require introducing new nodes, possibly as a reducible layer on top of the standard ET nodes.
Option 2 could run into problems where tuple conversions require temporaries and in the ET version (1.0) those are not available.
It may be possible to use member bindings to avoid this problem, but it is not completely clear if that is possible and it will require that tuple conversion lowering in a context of expression trees to be significantly different.
Option 1 seems more attractive to me at the moment.
which status on this?
What is preventing this from being implemented via Option 1?
See also https://github.com/bartdesmet/ExpressionFutures/blob/master/CSharpExpressions/Microsoft.CSharp.Expressions/Microsoft/CSharp/Expressions/TupleLiteralCSharpExpression.cs
Any news about this 4 years old proposal?
Any news about this 4 years old proposal?
Nope. No news.