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

Why not support SequenceReader #191

Closed
oven425 opened this issue Dec 31, 2024 · 1 comment
Closed

Why not support SequenceReader #191

oven425 opened this issue Dec 31, 2024 · 1 comment

Comments

@oven425
Copy link

oven425 commented Dec 31, 2024

SequenceReader can read string, improve work
but not use in net472, can explanation reason?
thank you

@ericstj
Copy link
Member

ericstj commented Feb 11, 2025

SequenceReader was introduced after the System.Memory package was shipped and placed in servicing. The type was only added to .NETCore 3.0 and later. Once we ship an OOB like this that forwards types into the framework/corelib we do not add more API to the OOB. Doing so constrains API development in the latest framework due to restrictions around adding members to existing types / supporting different type locations across different versions, etc. You are free to take a copy of the SequenceReader source and use it internally on .NET Framework.

At this point we aren't taking feature requests / new API to these packages. We're only building them to support security updates.

cc @dotnet/area-system-memory @jkotas @stephentoub

@ericstj ericstj closed this as completed Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants