Support reproducible Wave artifacts across source and build directory locations

Abierto
  • ¿Algo no está bien?
#182 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@LunaStev ya está trabajando en esto.

Desde el 2/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Planned for v0.0.3-beta; reviewed against master cd13f1d9c244cfdb207f38412db6c513bd5fd543.

Vex fingerprints local inputs for safe reuse, but cache correctness is separate from producing identical distributable bytes in different directories. Whale needs portable module artifacts and provenance from independent builds.

Acceptance:

  • Define typed reproducibility/path-remapping settings backed by verified wavec capabilities. Document which fields are supported and reject unsupported settings before compilation.
  • Apply settings consistently to sources, generated/intermediate paths and debug/source paths where supported; retain usable diagnostics and local dependency files.
  • Keep portable provenance free of accidental source/build/cache-home paths. Local depfiles and diagnostic paths may remain absolute under their own contracts.
  • Include effective settings, compiler/std identity, target/profile/features and relevant tool identity in freshness/results. Cache keys need not be identical across directories.
  • Build the same fixture from two separate source and build roots and compare complete artifact bytes and portable records, including paths containing spaces/Unicode.
  • Explain remaining external linker/SDK/archive inputs; fail or report unsupported reproducibility guarantees instead of treating one matching hash as universal host support.

This extends #48/#59/#70. Wave compiler functionality missing from its public contract must be tracked as an explicit prerequisite, not emulated with unvalidated flags. Static-archive determinism belongs with the archive-output issue.

Starting points: profiles, invocation, freshness.

Integration dependencies: #181.

Lenguaje dominante
Rust
Estrellas
1
Forks
3
Merge medio
23 h 3 min
PR fusionados (30 d)
7

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/Vex

Todos los issues de wavefnd/Vex

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.