Architecture Overhauls

Abierto
#4 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Refactorización
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
rust
Área
build-system

Línea de trabajo

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.

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

Descripción

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
Lenguaje dominante
Rust
Estrellas
248
Forks
13
Merge medio
7 h 52 min
PR fusionados (30 d)
5

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

Todos los issues de DioxusLabs/rustd

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.