Question
Is shared_memory still being actively maintained?
I noticed:
- Last commit on
master: ~Jan 2023 (fda4134)
- Last push: ~Sep 2023
- ~15 open issues, several PRs sitting unmerged
I just filed #118 to bump nix from 0.23 → 0.30, which is required to build shared_memory under the OpenHarmony Tier-2 Rust targets (*-unknown-linux-ohos). The patch itself is small and mechanical, but I'd love to know:
- Are PRs being reviewed at all right now? Should I expect a response, or is the project effectively in caretaker mode?
- Is there interest in adding a co-maintainer? This crate is depended on by some fairly large downstreams (e.g. it's pulled in transitively by the
vite+ toolchain via vite-task), and a small backlog of dependency bumps + cross-platform fixes is accumulating.
- If neither of the above, would you consider transferring or blessing a fork?
Not trying to be pushy — totally understand life happens and OSS maintenance is hard. Just trying to figure out the right path forward so downstream users (myself included) know whether to wait, fork, or help.
Thanks for the crate, it's been useful! 🙏
Question
Is
shared_memorystill being actively maintained?I noticed:
master: ~Jan 2023 (fda4134)I just filed #118 to bump
nixfrom 0.23 → 0.30, which is required to buildshared_memoryunder the OpenHarmony Tier-2 Rust targets (*-unknown-linux-ohos). The patch itself is small and mechanical, but I'd love to know:vite+toolchain viavite-task), and a small backlog of dependency bumps + cross-platform fixes is accumulating.Not trying to be pushy — totally understand life happens and OSS maintenance is hard. Just trying to figure out the right path forward so downstream users (myself included) know whether to wait, fork, or help.
Thanks for the crate, it's been useful! 🙏