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

Fix null forgiving F1 keyword #20341

Merged
merged 1 commit into from
Sep 8, 2020
Merged

Conversation

Youssef1313
Copy link
Member

@Youssef1313 Youssef1313 commented Aug 28, 2020

@Youssef1313
Copy link
Member Author

@BillWagner Once dotnet/roslyn#47516 is reviewed for correctness, this should be ready to merge, then Roslyn's PR.

Copy link
Contributor

@davidwengier davidwengier left a comment

Choose a reason for hiding this comment

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

I don't think there is any reason to wait for the Roslyn PR to be approved, having the same f1_keyword in two pages is a problem regardless of whether any code currently points to it.

Copy link
Contributor

@davidwengier davidwengier left a comment

Choose a reason for hiding this comment

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

I don't think there is any reason to wait for the Roslyn PR to be approved, having the same f1_keyword in two pages is a problem regardless of whether any code currently points to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue with !_CSharpKeyword
5 participants