Skip to content

[C# 14-Fundamentals and reference]: New Feature - Partial events and constructors #45185

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

Closed
BillWagner opened this issue Mar 10, 2025 · 0 comments · Fixed by #45336
Closed

[C# 14-Fundamentals and reference]: New Feature - Partial events and constructors #45185

BillWagner opened this issue Mar 10, 2025 · 0 comments · Fixed by #45336
Assignees
Labels
🏁 Release: .NET 10 Work items for the .NET 10 release dotnet-csharp/svc in-pr This issue will be closed (fixed) by an active pull request. 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer whats-new/subsvc

Comments

@BillWagner
Copy link
Member

BillWagner commented Mar 10, 2025

Visual Studio release

None

Link to speclet

Link to Pull request

New behavior

The surface area isn't large: partial members can now include constructors and events.

Changes needed:

  • Publish speclet
  • Update language reference on partial keyword.
  • Update What's new in C# 14
  • Search for other mentions of partial and make sure they don't incorrectly exclude partial events and constructors.

Not adding a separate issue for errors, because that should be covered by #45117

Language reference tasks

No response

Everyday C# tasks

No response


Associated WorkItem - 410370

@BillWagner BillWagner self-assigned this Mar 10, 2025
@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Mar 10, 2025
@BillWagner BillWagner added 🗺️ reQUEST Triggers an issue to be imported into Quest. and removed ⌚ Not Triaged Not triaged labels Mar 11, 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 11, 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 11, 2025
@BillWagner BillWagner moved this from 🔖 Ready to 🏗 In progress in dotnet/docs March 2025 sprint project Mar 11, 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 11, 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 11, 2025
@dotnet-policy-service dotnet-policy-service bot added the in-pr This issue will be closed (fixed) by an active pull request. label Mar 13, 2025
@BillWagner BillWagner moved this from 🏗 In progress to 👀 In review in dotnet/docs March 2025 sprint project Mar 13, 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 13, 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 13, 2025
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in dotnet/docs March 2025 sprint project Mar 14, 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 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏁 Release: .NET 10 Work items for the .NET 10 release dotnet-csharp/svc in-pr This issue will be closed (fixed) by an active pull request. 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer whats-new/subsvc
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant