2025 All Hands Topics

Performance Roadmap

Discuss https://hackmd.io/-jpsOWYoRACRNF3G80Hkuw?edit

Other teams:

  • T-compiler

XDG Paths

Discuss https://internals.rust-lang.org/t/pre-rfc-split-cargo-home/19747/56

Other teams:

  • T-rustup

Doctests

Other teams:

  • T-rustdoc
  • T-compiler?
  • T-lang?

Cargo Lints

  • The rustc (as part of build) vs clippy (explicit operation) split apply to cargo?
    • Should we use the same workflow (cargo check vs cargo clippy)
    • Or do users need to know of a separate workflow they need to opt-in to for these lints (a config, a flag, a new command)
  • What namespaces should we use for cargo lints
    • Some lints mirror existing common namespace (deprecated, etc)
    • Some will behave clippy-like
    • Some will be unique to cargo but rustc-like
    • Currently, warnings applies to all existing namespaces (common, clippy)
  • Should RUSTFLAGS=-Awarnings apply to Cargo's linting?
    • No, RUSTFLAGS is for Rust source code (except target.*.dependencies)
    • Yes to all
    • Only to those namespaces already affected by RUSTFLAGS (common, clippy)
  • If Cargo uses the common namespace, how much of the metadata should be determined at runtime vs build time (ie calling rustc just to get flag state)

See also https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/Sharing.20of.20lints/near/475872847

Select a repo