Skip to content

Add latest errors and warnings from C# 13 - 14 #45117

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.

Sign up for GitHub

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

Jump to bottom
Open
BillWagner opened this issue Mar 4, 2025 · 1 comment
Open

Add latest errors and warnings from C# 13 - 14 #45117

BillWagner opened this issue Mar 4, 2025 · 1 comment
Assignees
@BillWagner
Labels
dotnet-csharp/svc errors-warnings/subsvc okr-curation OKR: Curate content to remove outdated recommendations 📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@BillWagner
Copy link
Member

BillWagner commented Mar 4, 2025 •
edited by sequestor bot
Loading

Type of issue

Missing information

Description

There are some errors and warnings in C# 13 and C# 14 that haven't been documented. Add them

Page URL

https://learn.microsoft.com/en-us/dotnet/csharp/misc/sorry-we-don-t-have-specifics-on-this-csharp-error

Content source URL

https://github.com/dotnet/docs/blob/main/docs/csharp/misc/sorry-we-don-t-have-specifics-on-this-csharp-error.md

Document Version Independent Id

58a19505-ac46-c5c8-12cc-fe87b6aa18a7

Article author

@BillWagner

Metadata

  • ID: bbb051ee-f020-66ba-c601-4a08ad32ef61
  • PlatformId: 8acee5cb-4bef-a4f2-edd5-e8e236844c4e
  • Service: dotnet-csharp
  • Sub-service: errors-warnings

Related Issues

Associated WorkItem - 402709
@BillWagner BillWagner self-assigned this Mar 4, 2025
@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Mar 4, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 4, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 4, 2025
@BillWagner BillWagner added 🗺️ reQUEST Triggers an issue to be imported into Quest. 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. and removed ⌚ Not Triaged Not triaged labels Mar 4, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 4, 2025
@BillWagner BillWagner added the okr-curation OKR: Curate content to remove outdated recommendations label Mar 4, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Mar 5, 2025
@BillWagner BillWagner mentioned this issue Mar 10, 2025
Closed
@BillWagner BillWagner moved this from 🔖 Ready to Slipped in dotnet/docs March 2025 sprint project Apr 2, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@BillWagner
Copy link
Member Author

Include the new errors are warnings introduced as part of #45610 and #45611

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BillWagner BillWagner

Labels
dotnet-csharp/svc errors-warnings/subsvc okr-curation OKR: Curate content to remove outdated recommendations 📌 seQUESTered Identifies that an issue has been imported into Quest.
Projects
dotnet/docs April 2025 sprint project
Status: 🔖 Ready
dotnet/docs March 2025 sprint project
Status: Slipped
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BillWagner