Define partial-overlap semantics for bounded C-string copying
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
- 35/100
Línea de trabajo
Start with the bounded C-string copy implementation at std/mem/cstr.wave:67 and review the related exact-alias behavior in #854. Before changing code, get the maintainer discussion requested for the partial-overlap contract, including dst=src, src+1, and src-1 cases. Done means the documented success, truncation, NUL-placement, and output-change rules cover every permitted case, and the implementation and tests reject or support each alias shape consistently without regressing the exact-alias fix.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Motivation
Exact source/destination alias truncation was fixed in #854. With dst=src+1, the current forward copy of abc repeatedly observes its own writes, returns no-space and fills the available destination with a. Whether partial overlap is allowed is unspecified; this is not another report of the fixed exact-alias defect.
Starting point: std/mem/cstr.wave:67.
Validation
Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Executed bounded valid-memory partial-overlap fixture at 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
Decide whether partial overlap is rejected/preconditioned or gets memmove-like behavior, including NUL placement and truncation side effects. Keep the exact-alias fix intact.
Related: #854. 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
- Cover dst=src, src+1 and src-1 with valid bounded storage.
- The documented success/truncation/output-change contract matches all permitted cases.
- No unsupported alias shape is silently advertised as safe.
- Lenguaje dominante
- Rust
- Estrellas
- 56
- Forks
- 21
- Merge medio
- 10 h 10 min
- PR fusionados (30 d)
- 52
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de wavefnd/Wave
-
bug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
bug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
bug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
build good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
discussion enhancement help wanted
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
Todos los issues de wavefnd/Wave
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
FalkorDB/FalkorDB#3597 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
mozilla-services/syncstorage-rs#2715 ·
Los mantenedores suelen responder en 1 día