Skip to content

API should allow accepting Memory-specific types instead of byte[] #403

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
Open
lukebakken opened this issue Feb 25, 2025 · 0 comments
Open

API should allow accepting Memory-specific types instead of byte[] #403

lukebakken opened this issue Feb 25, 2025 · 0 comments
Labels
enhancement New feature or request
Milestone
2.0.0

Comments

@lukebakken
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Users would like to avoid copying memory as much as possible. Version 2 of this library should facilitate that.

Related to:

Describe the solution you'd like

Accept IMemoryOwner or similar arguments to API methods that currently accept byte[]

Describe alternatives you've considered

N/A

Additional context
@lukebakken lukebakken added the enhancement New feature or request label Feb 25, 2025
@lukebakken lukebakken added this to the 2.0.0 milestone Feb 25, 2025
@lukebakken lukebakken changed the title API should allow accepting API should allow accepting Memory-specific types instead of byte[] Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
1 participant
@lukebakken