System.Buffers work planned for .NET 8

[dakersnar]

This is a work in progress as we develop our .NET 8 plans. This list is expected to change throughout the release cycle according to ongoing planning and discussions, with possible additions and subtractions to the scope.

Summary

We are not planning many notable investments into the System.Buffers area in .NET 8. This list may be added to as the year progresses.

Planned for .NET 8

• [API Proposal]: Utf8Formatter/Utf8Parser should have UInt128 and Int128 overloads #73842
• Regressions from JitConsumeProfileForCasts #71068
• ArrayPool trimming does not respect GCHardLimit #853
• ReadOnlySequence<T> GetOffset does not function correctly with non-zero starting indices #75866

[ghost]

Tagging subscribers to this area: @dotnet/area-system-buffers
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This issue captures the planned work for .NET 8. This list is expected to change throughout the release cycle according to ongoing planning and discussions, with possible additions and subtractions to the scope.

Summary

We are not planning many notable investments into the System.Buffers area in .NET 8. This list may be added to as the year progresses.

Planned for .NET 8

• [API Proposal]: Utf8Formatter/Utf8Parser should have UInt128 and Int128 overloads #73842
• Regressions from JitConsumeProfileForCasts #71068
• ArrayPool trimming does not respect GCHardLimit #853

Author:	dakersnar
Assignees:	jeffhandley, tannergooding, dakersnar, michaelgsharp
Labels:	Epic, area-System.Buffers, Team:Libraries
Milestone:	8.0.0

[tannergooding]

Closing as this was a meta issue.

The core work got completed. Various non-critical bits were pushed out or not worked on.