make runtime library loading safer
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Thursday Jun 19, 2014 at 17:17 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/15040
This issue was labelled with: A-an-interesting-project, A-libs, E-hard, I-enhancement in the Rust repository
We currently have an interface for runtime library loading, using the dynamic linker, but it has the problem that it interacts poorly with name mangling and is entirely unsafe. Figure out how to make it type-safe, and preferably memory-safe too.
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 15040 and the std::dynamic_lib documentation linked in the issue. Investigate how dynamic linking currently interacts with Rust name mangling and unsafe APIs. Done would require a concrete approach that makes runtime library loading type-safe and preferably memory-safe.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100