Skip to content

Fixes around identifier and type mappings for ValuesExpression#33439

Merged
roji merged 1 commit into
dotnet:mainfrom
roji:InlineCollectionStuff
Mar 31, 2024
Merged

Fixes around identifier and type mappings for ValuesExpression#33439
roji merged 1 commit into
dotnet:mainfrom
roji:InlineCollectionStuff

Conversation

@roji
Copy link
Copy Markdown
Member

@roji roji commented Mar 30, 2024

@maumar the identifier fix doesn't have a test for it - not sure I can come up with a test case that doesn't also involve a set operation, which is blocked by other issues (#33410 (comment)).

Closes #33436
Closes #33438

@roji roji requested a review from maumar March 30, 2024 16:06
@maumar
Copy link
Copy Markdown
Contributor

maumar commented Mar 30, 2024

Test with Union should work. For that we ignore the original identifiers (as long as there were some to begin with) and use the projection itself as identifier. @roji

@roji roji force-pushed the InlineCollectionStuff branch from 897d104 to 892fe6a Compare March 30, 2024 21:54
@roji roji force-pushed the InlineCollectionStuff branch from 892fe6a to 2b507ab Compare March 30, 2024 22:59
@roji
Copy link
Copy Markdown
Member Author

roji commented Mar 30, 2024

@maumar thanks for the tip, makes sense! Pushed the UNION-based test, and some other fixes, should be ready for review.

@roji roji merged commit c89731a into dotnet:main Mar 31, 2024
@roji roji deleted the InlineCollectionStuff branch March 31, 2024 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Infer inline collection element type mappings from each other (and onto the projection) Set the ordering as the identifier when translating VALUES

2 participants