Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Latent
NullReferenceExceptionwhen the first feature entry has version−1resultstarts asdefault(T)—nullfor any reference-typeT. The tie-breaker armversion == maxVersionfires the moment a feature entry's version matches the initial sentinel value of−1(i.e.Features[entry.Feature] == -1). If that happens before any prior entry has setresult, the expressionresult.Featuredereferences a null object and throws.Note that
string.Compareitself is null-safe for its string arguments (one or both comparands can be null — by definition, any string compares greater than a null reference), so the problem is specifically the member access onresult, not the comparison call.The correct guard also covers the semantics correctly: a null
resultshould always be replaced by any feature entry at the same version (just as any feature beats no-feature).🛡️ Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents