dotnet/roslyn

Nullability no longer honors null check when it is also an assignment

Open

#44,461 opened on May 21, 2020

View on GitHub
 (1 comment) (2 reactions) (1 assignee)C# (4,257 forks)batch import
Area-CompilersBugFeature - Nullable Reference Typeshelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

Version Used: master (19 May 2020)

Steps to Reproduce:

  1. Do assignment of the null check expression inside an if statement.

Repro code: https://sharplab.io/#v2:EYLgtghgzgLgpgJwDQBMQGoA+BiAdgVwBtCJhC4ACOXU8gWACgABAJgEZGmBmC1igYQoBvRhTG8eTACwUAsgAoAlMNHi1qtWIBiAex0UAZhQC8FXHADuFXTqUBuDZsdrgewhQCWUAHJFCDhk1xDyN5L19iE0MAOgAFBB0AB0QYAE8KAEJTAmJFZ3ERQKDNJjYATnkDOITkhDTogBUdABkdC0QlRQDiigBfR36GQc5JFms9RkK1bl42AAYAfgp4pJT0oQoAczgYOwooHb3B3qA===

Expected Behavior: Object was already checked for null, nullability should no longer warn "Possible null reference".

Actual Behavior: Nullability still warn "Possible null reference" regardless of the previous null check.

cc @jaredpar @cston @jcouv

Contributor guide

Research direction
Investigate how the Roslyn nullable flow analysis handles assignments within null checks, specifically in 'if' statements. Trace the control flow graph and ensure the null state is updated after the assignment.
Tech stack
csharp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30