add a low-level library for manipulating memory mappings, protection and locking
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Saturday Sep 06, 2014 at 18:13 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/17047
This issue was labelled with: A-libs, I-enhancement in the Rust repository
Rust should expose a portable implementation of the mmap, mprotect and mlock functionality (VirtualAlloc, VirtualProtect, VirtualLock on Windows). The current support for memory mapped files is very lacking. The low-level support should be exposed via unsafe functions, and then a new high-level wrapper can be written on top of it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the earlier discussion in rust-lang/rust issue 17047 and the surrounding RFC context. Define the portable low-level scope for memory mapping, protection, and locking across Unix and Windows, then determine how unsafe functions and a higher-level wrapper should relate. Done means the agreed API and portability requirements are documented and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100