Skip to content

Coupling all xtasks into one binary can hurt performance #2

@epage

Description

@epage

Some xtasks a developer will want to run regularly (like bundling up artifacts for wasm or embedded as part of their debug cycle). Some developers might rarely run, like some code-gen.

Similar for a CI. Multiple independent jobs will need to build the xtasks. Most jobs will just need the ones related to CI. Only one job will need to validate code-gen. Only a couple of jobs, conditioned on version tags, will need to call xtask dist.

By putting all of these into a single binary, we're losing out on performance by requiring it to build dependencies or run build scripts for xtasks that won't be run

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions