Define readonly string-literal storage for the Whale subset

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

Línea de trabajo

Start by reading whale/src/codegen/expression.rs and the current GlobalStorage validation, then run the matching checkout-built compiler probes for string rejection and global-storage type restrictions. The issue identifies wave/src/codegen/expression.rs:23 as the starting point and requires an approved upstream representation before implementation. Done means documenting the representation, then verifying bounded reads/indexing and agreed write rejection without host pointer embedding or silent LLVM fallback.

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

Descripción

discussion enhancement help wanted

Motivation

A local str="ok" and text[0] succeeds in the LLVM language path but Whale reports unsupported type String. Official current GlobalStorage validation is scalar-only; its readonly flag is not proof that a byte-array string can already be represented.

Starting point: whale/src/codegen/expression.rs:23.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Executed Whale string rejection and read official global-storage type restrictions. 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

Coordinate a supported readonly byte-storage representation with upstream, including NUL bytes, lifetime, pointer provenance and initialization. Track it after #996 and pointer support, without pretending aggregate global storage already exists.

Related: #996, #879, #880. 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

  • Document any required upstream representation first.
  • The approved subset verifies and executes bounded reads/indexing and rejects writes as agreed.
  • No host pointer embedding, silent LLVM fallback or native-execution claim.
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.