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 Reference Types] Provide informative notes and examples on diagnostics #1094

Open
Tracked by #1085
BillWagner opened this issue Apr 26, 2024 · 2 comments · May be fixed by #1192
Open
Tracked by #1085

[Nullable Reference Types] Provide informative notes and examples on diagnostics #1094

BillWagner opened this issue Apr 26, 2024 · 2 comments · May be fixed by #1192
Assignees
Labels
meeting: discuss This issue should be discussed at the next TC49-TG2 meeting

Comments

@BillWagner
Copy link
Member

We likely need some informative examples for static null state flow analysis and the diagnostics that might be produced.

As we complete the normative information, we will have a better idea what examples or notes will help readers understand the feature, its benefits, and the diagnostics.

@BillWagner BillWagner added the meeting: discuss This issue should be discussed at the next TC49-TG2 meeting label Sep 18, 2024
@BillWagner
Copy link
Member Author

Let's add this to the end of the agenda (after discussing NRT, #1092, #1093). If we have some guidance on how far to go on this route, it would help me create a PR for November.

@BillWagner
Copy link
Member Author

We want one or two reasonable analysis examples can show some of the concepts of the analysis a compiler might do.

Maybe consider one or two where the "best effort" can be defeated.

@BillWagner BillWagner linked a pull request Oct 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meeting: discuss This issue should be discussed at the next TC49-TG2 meeting
Projects
No open projects
Status: 👀 In review
Development

Successfully merging a pull request may close this issue.

1 participant