Specify when NetEvent.fd is valid across readiness backends

Abierto
  • ¿Algo no está bien?
#1,013 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
backend-api-design, operating-systems

Línea de trabajo

Start with std/sys/linux/event.wave:18 and trace NativeEvent production through the public NetEvent facade in net_event_wait. Review the Linux, kqueue, and Windows backends to identify their current fd and token behavior. Completion requires an explicitly agreed portable validity contract, tested rules for every backend, and examples using only fields guaranteed by that contract; implementation should wait for design discussion with @LunaStev.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

discussion enhancement help wanted

Motivation

The Linux provider returns fd=-1 while preserving the caller token; kqueue and Windows providers return a descriptor. net_event_wait copies this field into the public NetEvent without a field-validity contract. Portable consumers cannot know whether fd is usable.

Starting point: std/sys/linux/event.wave:18.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Traced NativeEvent production through the public NetEvent facade. 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.

Scope

Choose a stable token-first/optional-fd or always-valid-fd contract and document the representation without implying native backend parity.

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

  • Every backend has a tested, explicit NetEvent.fd validity rule.
  • Tokens retain full identity and descriptor reuse does not create stale associations.
  • Examples use only fields guaranteed by the portable contract.
Lenguaje dominante
Rust
Estrellas
56
Forks
21
Merge medio
23 h 20 min
PR fusionados (30 d)
45

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de wavefnd/Wave

Todos los issues de wavefnd/Wave

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.