Support reproducible Wave artifacts across source and build directory locations

Aperta
  • Qualcosa non va?
#182 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@LunaStev ci sta già lavorando.

Dal 2/11/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.

Lingua principale
Rust
Stelle
1
Fork
3
Merge medio
23h 3m
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wavefnd/Vex

Tutte le issue di wavefnd/Vex

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.