Skip to content

cargo fix checks packages serially, even if there is nothing to fix #13214

New issue
New issue
Open
Open
cargo fix checks packages serially, even if there is nothing to fix#13214

Description

@epage

epage
openedon Dec 29, 2023

Problem

Running cargo fix (and worse, cargo clippy --fix on https://github.com/crate-ci/typos is very slow. For clippy, its over 2m.

Proposed Solution

Packages are checked serially. Seems like we could speculatively check them in parallel in case nothing is affected.

Notes

See also https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/Performance.20of.20.60cargo.20fix.60

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Command-fixPerformanceGotta go fast!S-needs-designStatus: Needs someone to work further on the design for the feature or fix. NOT YET accepted.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions