[CSHARP-4542] LINQ3 support for projecting to a ValueTuple<> Created: 22/Feb/23 Updated: 09/Mar/23 Resolved: 09/Mar/23 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | LINQ3 |
| Affects Version/s: | 2.19.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Damith G | Assignee: | Robert Stam |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
||||||||||||||||
| Description |
|
the following code results in an expression not supported exception in LINQ3 while it used to work with LINQ2:
stack trace:
however projecting to a Tuple<> works just fine. |
| Comments |
| Comment by Robert Stam [ 09/Mar/23 ] |
|
I have verified that Note however that once |
| Comment by Robert Stam [ 23/Feb/23 ] |
|
The code review is of the reproduction and the proof that There are no driver changes involved. |
| Comment by Robert Stam [ 23/Feb/23 ] |
|
The difference between `Tuple` and `ValueTuple` is that `Tuple` has properties called `Item1` etc and `ValueTuple` has fields called `Item1` etc. That means that this is actually a duplicate issue of |
| Comment by Robert Stam [ 22/Feb/23 ] |
|
Thanks for reporting this issue. We can definitely support this. I will look into it soon |