Define duplicate registration behavior for portable event_add

Aperta
  • Qualcosa non va?
#1,011 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, rust
Ambito
backend-api-design, operating-systems

Direzione di ricerca

Start by reading std/sys/macos/event.wave:66 and comparing it with the Linux, Windows, and kqueue event-provider sources plus the documented kqueue semantics. Before implementation, discuss the add-versus-modify and token-ownership contract with @LunaStev, as the issue explicitly leaves the design unresolved. Done means each backend has documented same-token and different-token duplicate-add behavior, consistent modify/remove interactions, and native or backend-boundary fixtures covering the complete sequence.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

discussion enhancement help wanted

Motivation

Linux epoll ADD and the Windows set reject an already registered descriptor, while kqueue EV_ADD updates an existing ident/filter registration. The portable facade exposes these as the same add operation without defining the duplicate/token replacement contract.

Starting point: std/sys/macos/event.wave:66.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Compared Linux/Windows/kqueue provider source and official kqueue semantics. Executed compiler probes use the matching checkout-built compiler and std on Linux amd64 (Rust 1.89.0 / LLVM 21.1.8). Source/header or mocked checks are not native execution on another OS.

FreeBSD kqueue(2) specifies that re-adding modifies an existing event.

Scope

Choose consistent add-versus-modify and token ownership semantics, or make the capability difference explicit. Do not silently rely on one backend's behavior.

Design discussion required

This issue records a proposal or an unresolved contract; it is not approval to choose new semantics. Please mention @LunaStev to discuss the design before starting implementation.

Completion criteria

  • Duplicate add with the same and different tokens has a documented result on each backend.
  • Modify/remove interactions follow the same ownership contract.
  • Native/backend-boundary fixtures check the complete sequence.
Lingua principale
Rust
Stelle
56
Fork
21
Merge medio
23h 20m
PR unite (30g)
45

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wavefnd/Wave

Tutte le issue di wavefnd/Wave

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.