Skip to content

Tracking issue for config-include #7723

Open

Description

Implementation: #7649
Original proposal: #6699
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#config-include
Issues: Z-config-include Nightly: `include` config key

Summary

Adds the include config key to include other config files.

Unresolved issues

  • Should there be any restriction on the filename? Currently there isn't. I was initially considering restricting to .cargo/config-* in case we want to safely use other filenames in .cargo/ for other purposes. However, it seems like an unnatural restriction. Another restriction is that it should maybe end in .toml?

FCP

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-tracking-issueCategory: A tracking issue for something unstable.S-waiting-on-feedbackStatus: An implemented feature is waiting on community feedback for bugs or design concerns.T-cargoTeam: CargoZ-config-includeNightly: `include` config keydisposition-mergeFCP with intent to mergeproposed-final-comment-periodAn FCP proposal has started, but not yet signed off.

    Type

    No type

    Projects

    • Status

      Unstable, baking
    • Status

      FCP blocked

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions