Skip to content

Possible bug in the flow analysis of nullable reference types #39424

@johnknoop

Description

@johnknoop

I've just enabled the new nullable reference types feature.

In this example, myObj is nullable. But shouldn't the compiler understand that myObj won't be null in this case, since I'm testing for it in the if clause?

image

I'm using .NET Core 3.0 in VS 2019.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions