Define capacity semantics and backend limits for portable event loops

Abierto
  • ¿Algo no está bien?
#1,014 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
32/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
operating-systems

Línea de trabajo

Start with std/sys/windows/event.wave at the readiness capacity handling, then compare creation, registration, and wait boundaries in the epoll, kqueue, Windows readiness, and IOCP providers. Use compiler probes at capacities 0, 1, 64, and 65, plus registrations beyond capacity, to establish current behavior. Done means the contract separates the three capacities, defines target-specific or common outcomes and clear errors, and preserves existing event behavior after the design is agreed with @LunaStev.

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

Descripción

discussion enhancement help wanted

Motivation

The Windows readiness set enforces a fixed maximum and registration capacity, while epoll/kqueue creation uses a positive hint. The public loop capacity argument does not explain whether it is a hint or a portable registration limit.

Starting point: std/sys/windows/event.wave:45.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Compared creation/add/wait boundaries in all readiness providers. 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

Define creation capacity, registration capacity and per-wait output capacity separately. Preserve the bounded Windows readiness fallback and keep IOCP distinct.

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

  • Creation at 0/1/64/65 and registration beyond capacity have documented target-specific or common results.
  • Output capacity does not silently redefine registration capacity.
  • Unsupported limits produce clear errors and existing event behavior remains valid.
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.