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

Status of the crate #14

Open
dignifiedquire opened this issue Feb 2, 2022 · 1 comment
Open

Status of the crate #14

dignifiedquire opened this issue Feb 2, 2022 · 1 comment

Comments

@dignifiedquire
Copy link

Hey I am trying to understand some of the challenges around using shared memory in rust and found this crate through a rust-lang issue. Could you give me a short summary if there are known issues with this at the moment or not? thank you!

@asajeffrey
Copy link
Owner

Well, I'm not working on Rust at the moment, so this crate is unmaintained. The main issue with shared memory is that it's very difficult to stop it from being closed, so any read is unsafe, and it's difficult to see how to make it safe. If you assume that other processes don't do that, I think it's a safe abstraction. There might be a better trait for "data that has no layout requirements" these days.

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