You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should consider supporting deconstruction (tuples and general) in expression tree lambdas.
It can be done either by
Introducing new nodes that represent Deconstruction or
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 deconstruction 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 deconstruction lowering in a context of expression trees to be significantly different.
Option 1 seems more attractive to me at the moment.
The text was updated successfully, but these errors were encountered:
We should consider supporting deconstruction (tuples and general) in expression tree lambdas.
It can be done either by
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 deconstruction 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 deconstruction lowering in a context of expression trees to be significantly different.
Option 1 seems more attractive to me at the moment.
The text was updated successfully, but these errors were encountered: