WebAssembly / WebAssembly/WASI
Question on Non-Goal: network-related information
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
What was behind the decision of this non-goal:
Retrieving network-related information of the executing machine, like: installed network interfaces and the computer hostname.
To me this seems like a reasonable thing someone might want to have access to and enables creating network and diagnostic tools. If you're going to open up a raw socket for instance, wouldn't you want to know what interface you're doing it on? Or is that use-case another non-goal as well?
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
Start with the cited WASI non-goal and its rationale for excluding network interfaces and hostname access. Compare that scope with the raw-socket use case described in the issue. Done would be a documented decision clarifying whether this remains out of scope or what proposal is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100