WebAssembly / WebAssembly/WASI

TCP: SO_LINGER

Open
#709 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P-sockets S-inactive
Dominant language
Rust
Stars
5.8k
Forks
333
Avg merge
2d 13h
Merged PRs (30d)
3

Description

TODO:

  • SO_LINGER effectively turns the close syscall into a blocking function. How to model this in WIT?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the SO_LINGER TODO in issue #709 and review the surrounding WASI and WIT design context. Determine how a blocking close syscall should be modeled in WIT; done means the behavior has an agreed representation and the issue's design question is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
wasm
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.