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# 14-Fundamentals and reference]: New Feature - First class span #44183

Closed
BillWagner opened this issue Jan 8, 2025 · 0 comments · Fixed by #44641
Closed

[C# 14-Fundamentals and reference]: New Feature - First class span #44183

BillWagner opened this issue Jan 8, 2025 · 0 comments · Fixed by #44641
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 Jan 8, 2025

Visual Studio release

17.13.p3

Link to speclet

Link to Pull request

New behavior

This was merged into VS 17.13.p1

This feature is active in LangVersion 14.

This introduces first-class support for Span<T> and ReadOnlySpan<T> in the language, including new implicit conversion types and consider them in more places, allowing more natural programming with these integral types.

Note that this PR didn't add any new errors or warnings. There's no corresponding issue to update those.

Language reference tasks

This impacts implicit conversions, explicit conversions, and user defined conversions involving Span types.

In addition, it will have some impact on the overload resolution algorithm.

However, these changes don't introduce new syntax or new ways to work with Spans. Instead, they mean Spans work more naturally in more constructs.

Everyday C# tasks

No response


Associated WorkItem - 370945

@BillWagner BillWagner self-assigned this Jan 8, 2025
@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Jan 8, 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 Jan 8, 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 Jan 8, 2025
@BillWagner BillWagner removed the ⌚ Not Triaged Not triaged label Jan 9, 2025
@BillWagner BillWagner moved this from 🔖 Ready to 🏗 In progress in dotnet/docs January 2025 sprint project Jan 31, 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 Jan 31, 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 Jan 31, 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 Jan 31, 2025
@BillWagner BillWagner moved this from 🏗 In progress to Slipped in dotnet/docs January 2025 sprint project Jan 31, 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 Jan 31, 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 Feb 3, 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 Feb 3, 2025
@dotnet-policy-service dotnet-policy-service bot added the in-pr This issue will be closed (fixed) by an active pull request. label Feb 4, 2025
@BillWagner BillWagner moved this from 🔖 Ready to 👀 In review in dotnet/docs February 2025 sprint project Feb 5, 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 Feb 5, 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 Feb 5, 2025
@BillWagner BillWagner added the 🗺️ reQUEST Triggers an issue to be imported into Quest. label Feb 6, 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 Feb 7, 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
1 participant