Design an opt-in atomic whole-file replacement API

Abierto
  • ¿Algo no está bien?
#1,038 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
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
operating-systems

Línea de trabajo

Start with std/fs/file.wave:247 and inspect fs_write_all, io_write_all, and the existing rename provider boundaries before designing the opt-in API. The agreed contract must define candidate creation, permissions, symlinks, flush and rename behavior, cleanup, and the distinction between atomic visibility and crash durability. Done means failures preserve the old destination, provider-specific ownership and link behavior are explicit, and atomic visibility plus durability guarantees are tested and documented.

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

Descripción

discussion enhancement help wanted

Motivation

fs_write_all intentionally opens/truncates the destination before writing. That existing behavior is useful, but cannot preserve the old file if a later write fails; applications saving configuration need a separate opt-in replacement operation.

Starting point: std/fs/file.wave:247.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Inspected fs_write_all/io_write_all and existing rename provider boundaries. 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

Design same-directory candidate creation, permission/symlink handling, flush/rename and cleanup rules. Distinguish atomic visibility from crash durability and do not change existing fs_write_all semantics.

Related: #738, #382. 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 agreed API preserves the old destination on controlled write/close/activation failures.
  • Ownership, permissions and link behavior are explicit across providers.
  • Atomic visibility and durability guarantees are tested and accurately documented.
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.