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

[C# 13]: New Feature - ref struct interfaces #41206

Closed
3 of 5 tasks
BillWagner opened this issue May 31, 2024 · 0 comments · Fixed by #41948
Closed
3 of 5 tasks

[C# 13]: New Feature - ref struct interfaces #41206

BillWagner opened this issue May 31, 2024 · 0 comments · Fixed by #41948
Assignees
Labels
🏁 Release: .NET 9 Work items for the .NET 9 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. whats-new/subsvc

Comments

@BillWagner
Copy link
Member

BillWagner commented May 31, 2024

Visual Studio release

17.11p2

Link to speclet

Link to Pull request

New behavior

A new generic constraint allow ref struct allows a ref struct to implement that interface.

Areas affected

  • Add to What's new in C# 13: Add links to updated docs in the What's new in C# 13 article.
  • Update language reference: Detail the areas in the language reference that will be updated for this feature.
  • Update compiler messages: Add new (or updated) pages for new compiler messages. Include related message.
  • Include in Everyday C# section*: Is this new feature included in Everyday C#?
  • Tutorials: Are new tutorials required for this feature? If so, detail below

Language reference tasks

The where generic constraint page needs updated.
The page for ref struct needs to be updated to remove / update the restriction for implementing interfaces.

The F1 keyword for allows needs to be added to the generic where constraint page.

Programming guide content for generics should be examined.

Tutorial tasks

No response

Everyday C# tasks

No response


Associated WorkItem - 259821

@BillWagner BillWagner self-assigned this May 31, 2024
@dotnet-bot dotnet-bot added ⌚ Not Triaged Not triaged labels May 31, 2024
@BillWagner BillWagner added the 🗺️ reQUEST Triggers an issue to be imported into Quest. label May 31, 2024
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label May 31, 2024
@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 Jun 1, 2024
@BillWagner BillWagner moved this from 🔖 Ready to Slipped in dotnet/docs June 2024 sprint Jun 26, 2024
@BillWagner BillWagner moved this from 🔖 Ready to 🏗 In progress in dotnet/docs July 2024 Sprint Jul 10, 2024
@BillWagner BillWagner added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jul 15, 2024
@BillWagner BillWagner moved this from 🏗 In progress to 👀 In review in dotnet/docs July 2024 Sprint Jul 31, 2024
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in dotnet/docs July 2024 Sprint Jul 31, 2024
@dotnet-policy-service dotnet-policy-service bot added the in-pr This issue will be closed (fixed) by an active pull request. label Jul 31, 2024
@adegeo adegeo removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏁 Release: .NET 9 Work items for the .NET 9 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. whats-new/subsvc
Projects
Status: ✅ Done
Status: Slipped
Development

Successfully merging a pull request may close this issue.

3 participants