[release/9.0-staging] Fix DefaultIfEmptyIterator.TryGetElementAt returning default value for out-of-bounds indices #119844
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
…ment not found Co-authored-by: eiriktsarpalis <[email protected]>
…tElementAt Co-authored-by: eiriktsarpalis <[email protected]>
eiriktsarpalis
added
Servicing-consider
stephentoub
approved these changes
Sep 18, 2025
|
Tagging subscribers to this area: @dotnet/area-system-linq |
eiriktsarpalis
added
api-approved
|
Approved over email. |
eiriktsarpalis
added
Servicing-approved
jeffhandley
approved these changes
Sep 19, 2025
|
/ba-g known test failures. |
eiriktsarpalis
deleted the
backport/pr-119838-to-release/9.0-staging
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Backport of #119838 to release/9.0-staging
/cc @eiriktsarpalis @copilot
Customer Impact
We regressed the behavior of the
DefaultIfEmptyLINQ method resulting in incorrect results when chained withElementAtOrDefaultusing an out of bounds index.Regression
#98969
Testing
Added unit testing verifying the impacted behavior.
Risk
Low. Applies a straightforward fix to a simple bug.