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

[Feature] Span<T> #4400

Closed
3 tasks
JRAlexander opened this issue Feb 14, 2018 · 14 comments · Fixed by dotnet/dotnet-api-docs#548 or dotnet/dotnet-api-docs#194
Closed
3 tasks

[Feature] Span<T> #4400

JRAlexander opened this issue Feb 14, 2018 · 14 comments · Fixed by dotnet/dotnet-api-docs#548 or dotnet/dotnet-api-docs#194
Assignees
Labels
doc-idea Indicates issues that are suggestions for new topics [org][type][category]

Comments

@JRAlexander
Copy link
Contributor

JRAlexander commented Feb 14, 2018

Span<T>

This topic will address how to work with Span and related types. Span is a new type we are adding to the platform to represent contiguous regions of arbitrary memory, with performance characteristics on par with T[]. Its APIs are similar to the array, but unlike arrays, it can point to either managed or native memory, or to memory allocated on the stack.

Still Needed:

  • Content Types
  • Table of Contents
  • Prioritization
@davidfowl
Copy link
Member

davidfowl commented Feb 20, 2018

@mairaw mairaw added P1 labels Feb 20, 2018
@mairaw mairaw added this to the 2018 - Quarter 2 milestone Feb 20, 2018
@joshfree
Copy link
Member

@JimBobSquarePants
Copy link

Current 2.0 Docs are picking up on the obsolete attribute which is causing confusion.

https://docs.microsoft.com/en-us/dotnet/api/system.span-1?view=netcore-2.0

@mairaw
Copy link
Contributor

mairaw commented Apr 10, 2018

Thanks @JimBobSquarePants. This seems related to the following issues that we're tracking:
https://github.com/dotnet/docs/issues/1876
mono/api-doc-tools#76

@weshaggard I see that the obsolete attribute was added with the addition of the .NET Core 2.1 reference assemblies. Is Span<T> really marked as obsolete in 2.1?

@JimBobSquarePants
Copy link

@ahsonkhan
Copy link
Member

cc @VSadov

@mairaw
Copy link
Contributor

mairaw commented Apr 17, 2018

I've created a workaround PR to fix the obsolete attribute issue while the true fix is being worked out:
dotnet/dotnet-api-docs#49

@OnurGumus
Copy link
Contributor

@mairaw Obsolete attribute blocks the F# compiler for span.

@mairaw
Copy link
Contributor

mairaw commented Apr 27, 2018

@cartermp can you look at this previous comment?

@cartermp
Copy link
Contributor

It doesn't affect these docs. When we take a look at proper span support in the F# compiler that particular issue will be addressed.

@OnurGumus
Copy link
Contributor

Perhaps this is not correct place to rant but there is a tendency to treat C#== .NET. It seems for BCL and runtime changes languages like F# is completely ignored or afterthought. Same things happened with .NET Native, ValueTuple, default interface implementations etc. I just wish things were more lang agnostic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-idea Indicates issues that are suggestions for new topics [org][type][category]
Projects
None yet
10 participants