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

Introduce a safe abstraction over UnsafeRawMutablePointer #3

Open
tristanlabelle opened this issue Jul 28, 2023 · 0 comments
Open

Introduce a safe abstraction over UnsafeRawMutablePointer #3

tristanlabelle opened this issue Jul 28, 2023 · 0 comments

Comments

@tristanlabelle
Copy link
Owner

We rely on memory mapping files and accessing them through UnsafeRawMutablePointer, but that type makes it possible and easy to construct byte ranges outside of the original Data. We should have an abstraction (ByteSpan?) which only allows creating contained subranges for safety.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tristanlabelle