Where should the loader itself sit?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
While initially it might seem like a platform concern, after a discussion, it seems like this is yet another somewhat cross-cutting concern that _mostly_ relies on the shim, with some possible features coming in from the platform. I believe that the loader is sufficiently shim-specific (i.e., the Linux shim and the Wasm shim would not have the same loader, and only might rely on a tiny amount of shared functionality to provide it), thus the loader should sit in the shim layer.
Contributor guide
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
The issue names no files, tests, or entry points. Start by reviewing the discussion and the existing shim and platform organization; done means an agreed loader ownership design is documented or implemented consistently for the affected shims.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust, wasm
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100