Integrate Whale linking only after executable and diagnostic contracts are implemented

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

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java, rust
Ambito
build-system, compilers

Direzione di ricerca

Start by reading the two linked files, Whale/src/commands/linker.rs and linker/src/core/linker.rs#L24, to see the placeholder stub and empty-output behavior. Then trace the blockers: sibling issues #51, #52, #56, #70 here and upstream Whale#62/#84/#87/#97/#116/#119 — the issue explicitly says implement only once those contracts exist. Done means a WfP adapter validating real link output identity/format, structured unresolved/duplicate-symbol diagnostics, the stub gated as unsupported, and stub/valid-link fake fixtures passing.

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

Descrizione

blocked upstream enhancement help wanted linker priority low whale

Problem / current evidence

The audited whale link CLI prints a placeholder and the library returns empty bytes. An exit code of zero currently does not establish that an executable was linked.

Code and contract references

Scope / proposed contract

After upstream real linking exists, add a WfP adapter for supported object/archive inputs, entry selection, link diagnostics and executable artifacts. Gate the current stub as unsupported.

Completion criteria

  • Require a real supported link contract and validate the expected output identity/format before recording success.
  • Show unresolved/duplicate symbols and associated object inputs using structured data where available.
  • Keep object order, target and entry explicit and preserve partial-failure logs.
  • Never execute a generated binary automatically after a link-only request.
  • Use stub/empty-output and valid-link fake fixtures; leave actual relocation and symbol resolution in Whale.

Dependencies and boundaries

  • Depends on #51.
  • Depends on #52.
  • Depends on #56.
  • Depends on #70.
  • Upstream prerequisites / contract coordination: Whale#62, Whale#84, Whale#87, Whale#97, Whale#116, Whale#119.
  • Blocked upstream: implement only once the prerequisite data/behavior described in this issue exists. Do not manufacture missing compiler semantics or report an unimplemented capability as supported.
  • Ecosystem index: #49; existing foundations: #8.

Difficulty

High — spans compiler contracts, process/debugger lifecycle or structured inspection.

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.