Architecture Overhauls

Aperta
#4 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à
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Refactoring
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
build-system

Direzione di ricerca

This issue lists broad architecture goals rather than a bounded change, and names no files or tests to start from. First read the existing architecture documentation and inspect the build graph, cache, and compiler backend entry points; choose one item only after its scope is defined. Done cannot be assessed until a specific goal and acceptance criteria are agreed.

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

Descrizione

This is a list of things I want to overhaul about rustd's architecture.

  • Instead of worker per workspace, aggregate all workspaces into a single build graph and optimize that. That way we can get cross-workspace sharing.
  • Shared build graph for test/clippy - this is a work in progress - would allow us to do clippy/test without paying a full recompile of the tip crates
  • Pick one of cranelift / llvm / llvm-tpde instead of supporting both. llvm o2 fast emit is close to cranelift. simpler to support
  • More disk caches for the analysis frontend. stress test disk caches all around
  • Ideally compile the entire tree with rustd and/or hybrid approach - if there's rustc artifacts we can reuse, reuse them and then rewire them with rustd.

General things we should have

  • fuzzing
  • replicated / normalized perf vs rustc directly
  • support for all rust point versions (1.98, 1.97, 1.96, etc) and nightlies? preventative rust maintenance
  • broader target support - funny arm variants, wasm variants, etc

General things todo:

  • human post processing of docs/language/code
  • proper release pipeline
  • proper downloads/artifacts page
  • proper docs
  • proper crater run infrastructure
  • blog post / how it works

Existing architecture bits

  • supports query overlays for fast worktree edits - however is a bit nerfed until the aggregate all workspaces thing is in
  • supports s3 / disk caches - ideal for CI - goal is incremental CI
  • supports splicing and hotpatching - two really fast linker shortcuts
Lingua principale
Rust
Stelle
248
Fork
13
Merge medio
7h 52m
PR unite (30g)
5

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 DioxusLabs/rustd

Tutte le issue di DioxusLabs/rustd

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.