Define Windows environment key matching independently from POSIX byte matching

Abierto
  • ¿Algo no está bien?
#1,009 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
compilers, operating-systems

Línea de trabajo

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.

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

Descripción

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.
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.