Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nullable annotation fixes #82803

Merged
merged 2 commits into from
Mar 3, 2023
Merged

Nullable annotation fixes #82803

merged 2 commits into from
Mar 3, 2023

Conversation

jaredpar
Copy link
Member

@jaredpar jaredpar commented Mar 1, 2023

Once runtime merges to a Roslyn toolset that has the fix for issue 50782 these annotations will be necessary. Front loading the work here with this change.

Once runtime merges to a Roslyn toolset that has the fix for [issue
50782](dotnet/roslyn#50782) these annotations
will be necessary. Front loading the work here with this change.
@ghost
Copy link

ghost commented Mar 1, 2023

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

Once runtime merges to a Roslyn toolset that has the fix for issue 50782 these annotations will be necessary. Front loading the work here with this change.

Author: jaredpar
Assignees: -
Labels:

area-Meta

Milestone: -

@jaredpar
Copy link
Member Author

jaredpar commented Mar 1, 2023

Can see the need for these demonstrated with #82615 where I was experimenting with latest compiler from main.

Copy link
Member

@stephentoub stephentoub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless the type is necessary to disambiguate, can all of these just be discards without the type name at all?

Co-authored-by: Stephen Toub <stoub@microsoft.com>
@jaredpar
Copy link
Member Author

jaredpar commented Mar 2, 2023

Unless the type is necessary to disambiguate, can all of these just be discards without the type name at all?

Sure thing. Was just trying to maintain existing style. happy to move to discards.

@jaredpar jaredpar merged commit a6975e0 into dotnet:main Mar 3, 2023
@jaredpar jaredpar deleted the nrt branch March 3, 2023 16:01
radical added a commit to radical/runtime that referenced this pull request Mar 3, 2023
`/workspaces/runtime/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessProxy.cs(135,44): error CS8601: Possible null reference assignment`

Started being hit with dotnet#82479 .
The other instances of this were fixed in
dotnet#82803 .
radical added a commit that referenced this pull request Mar 3, 2023
* [wasm] Debugger tests - fix build

`/workspaces/runtime/src/mono/wasm/debugger/DebuggerTestSuite/TestHarnessProxy.cs(135,44): error CS8601: Possible null reference assignment`

Started being hit with #82479 .
The other instances of this were fixed in
#82803 .

* CI: Trigger all the wasm jobs, when roslyn is updated

And this includes the debugger tests
@ghost ghost locked as resolved and limited conversation to collaborators Apr 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants