Inspect Whale assembler token AST and byte dumps without treating debug text as a protocol

Aperta
  • Qualcosa non va?
#67 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
cli, devtools

Direzione di ricerca

Start in Whale's src/commands/asm.rs (lines 108 and 316) where --debug-whale token/AST/byte dumps and dump-json are produced. First check dependency issue #65 and issue #8, since this work cannot start until they land. Done looks like: inspection presets that enable the required debug flag with each dump option, output panes separating token/AST text, byte samples and diagnostics, bounded samples explicitly labeled as partial, and fake stdout/stderr fixtures with mixed trace text proving no parsing of dbg! text and no assembly on edit.

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

Descrizione

assembler enhancement help wanted priority medium whale

Problem / current evidence

Whale offers --debug-whale token/AST/byte dumps, but token/AST use developer formatting and dump-json contains a length/head sample rather than a complete structured assembly model.

Code and contract references

Scope / proposed contract

Provide explicit inspection presets and read-only output tabs that preserve the original streams and label their limits. Do not parse dbg! text into a claimed stable AST.

Completion criteria

  • Enable the required debug flag alongside each selected dump option.
  • Keep token/AST text and byte samples separate from diagnostics and complete artifact contents.
  • Show when output is a bounded sample; do not imply dump-json contains all sections or bytes.
  • Allow comparison of captured outputs with invocation provenance.
  • Use fake stdout/stderr fixtures with mixed trace text; no automatic assembly on edit.

Dependencies and boundaries

  • Depends on #65.
  • Ecosystem index: #49; existing foundations: #8.

Difficulty

Medium — requires understanding the affected tool or platform integration.

Audit baseline: Wave 509a1e46; Whale e3a12d08; Vex 71f29daa; WfP 2804fc02. This issue records source-audit findings and proposed work; no implementation or new execution is claimed. The checks above are future acceptance criteria. Prefer small fixtures and targeted validation; full builds or real debugger/IDE sessions should be explicit and necessary.

Lingua principale
Java
Stelle
0
Fork
3
Merge medio
8h 8m
PR unite (30g)
1

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-for-platform

Tutte le issue di wavefnd/wave-for-platform

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.