WASM support
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 61
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The library compiles if you enable the "js" feature for uuid, but according to https://rustwasm.github.io/docs/book/reference/add-wasm-support-to-crate.html, direct I/O is a no-no, and norad is full of paths (as are UFOs). How could norad be rewritten to have the user be able to "bring their own I/O"?
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 with the issue body and the linked Rust and WebAssembly reference on adding WASM support to a crate. Map norad's direct I/O and path usage, then determine the scope of a user-provided I/O design; done would mean the library can operate under WASM without requiring direct I/O.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- tooling, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100