Fix parameter names for nested types in complex type equality #33527
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roji
force-pushed
the
ComplexTypeParameters
branch
from
d3f70ae to
1a0eac4
Compare
cincuranet
approved these changes
Apr 16, 2024
roji
added a commit
to roji/efcore
that referenced
this pull request
Apr 16, 2024
…#33527) Fixes dotnet#33449 (cherry picked from commit 89e9446)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #33449
Note: in extreme cases this may cause us to run up against maximum character limitations of parameter names (not sure we apply identifier limits there...).