Define Windows environment key matching independently from POSIX byte matching

Aperta
  • Qualcosa non va?
#1,009 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
compilers, operating-systems

Direzione di ricerca

Start by reading std/env/parse.wave:34 and the shared _env_match_key helper, then inspect the Windows environment provider and its lookup path. Coordinate with @LunaStev to approve the Windows comparison and Unicode contract before implementation. Done means mixed-case and Path/PATH queries follow that contract, hidden drive entries have defined behavior, POSIX remains case-sensitive, and native Windows amd64/arm64 facade tests pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

discussion enhancement help wanted

Motivation

The shared _env_match_key helper matches Path and rejects PATH against a Path=value block. The Windows provider preserves key spelling in the UTF-8 block, while Windows environment lookup is case-insensitive. Wave currently uses the shared byte-exact path.

Starting point: std/env/parse.wave:34.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Executed shared key matcher at O0/O2 and inspected Windows provider; no native Windows run. 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.

Microsoft environment-variable guidance distinguishes Windows from case-sensitive Linux/macOS variable names.

Scope

Decide the Windows key-comparison/Unicode contract while preserving POSIX case sensitivity. This concerns lookup after environment conversion, not the completed UTF-16 conversion work.

Related: #526. 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

  • Path/PATH and mixed-case queries follow the approved Windows contract.
  • Unicode and hidden drive entries have explicit behavior.
  • POSIX matching remains case-sensitive and native Windows amd64/arm64 tests cover the facade.
Lingua principale
Rust
Stelle
56
Fork
21
Merge medio
23h 20m
PR unite (30g)
45

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

Tutte le issue di wavefnd/Wave

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.