Define readonly string-literal storage for the Whale subset

Aperta
  • Qualcosa non va?
#1,035 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
compilers

Direzione di ricerca

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.

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

Descrizione

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