Define byte-cursor output aliasing with cursor state

Abierto
  • ¿Algo no está bien?
#1,037 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
compilers

Línea de trabajo

Start with std/bytes/read.wave:40, then locate the read and peek cursor-output variants and their tests. Before implementation, get the required design discussion with @LunaStev to decide whether cursor outputs may alias position, length, or backing storage. Done means the approved rule is documented for all alias cases, existing success and rollback behavior remains intact, and read/peek variants apply the same rule without per-width duplication.

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

Descripción

discussion enhancement help wanted

Motivation

Passing &reader.position as the u64 output of a valid eight-byte read returns success and leaves position=28 for len=8 when the decoded value is 20. O0/O2 agree. The API does not state whether output may overlap cursor state, and cannot simultaneously preserve two meanings for the same bytes.

Starting point: std/bytes/read.wave:40.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Executed valid-memory output/state alias fixture at native O0/O2. 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 explicit non-aliasing or checked-overlap rules for cursor outputs/state/backing storage. Do not promise arbitrary alias support or call this a Rust memory-safety defect.

Related: #674, #763. These links do not claim those broader or completed scopes are unfinished.

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

  • The position/len/data alias cases have documented permitted or rejected behavior.
  • Normal outputs and failure rollback keep their existing results.
  • Read and peek variants apply the same approved rule without duplicating one cause per integer width.
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.