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.

Sign up for GitHub

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

Jump to bottom

Remove all uses of IManagedByteBuffer #1675

Closed
JimBobSquarePants opened this issue Jun 20, 2021 · 0 comments · Fixed by #1730
Closed

Remove all uses of IManagedByteBuffer #1675

JimBobSquarePants opened this issue Jun 20, 2021 · 0 comments · Fixed by #1730
Labels
API breaking Signifies a binary breaking change.

Comments

@JimBobSquarePants
Copy link
Member

IManagedByteBuffer blocks any potential plans to use unmanaged memory as an optimization for our memory allocators. It's a legacy API used for older target frameworks but all use cases can now be replaced with IMemoryOwner<byte> since we have polyfilled the span APIs.

We should do so then remove the API.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API breaking Signifies a binary breaking change.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Unmanaged pooling MemoryAllocator SixLabors/ImageSharp
2 participants
@JimBobSquarePants @antonfirsov