Skip to content

support rust-toolchain-nightly.toml #4818

Description

@xoviat

Problem you are trying to solve

At embassy, we have the rust-toolchain.toml and rust-toolchain-nightly.toml files to specify the stable and nightly versions that we want to use. Currently we have scripts to remove rust-toolchain.toml and rename rust-toolchain-nightly.toml to switch to the nightly version, but it would be nicer to use cargo +nightly ... and have cargo use the nightly version in the nightly toolchain file, rather than the default nightly toolchain.

Solution you'd like

but it would be nicer to use cargo +nightly ... and have cargo use the nightly version in the nightly toolchain file, rather than the default nightly toolchain.

Notes

No response

Activity

  1. rami3l commented on Apr 18, 2026

    @rami3l
    Member

    @xoviat Thanks for reporting!

    As I understand it the historical context of rust-toolchain.toml is for gathering hard requirements for the development of a certain project because it depends on, say, the particular state (of unstable features) of a given nightly, and it has no intention of becoming the "recommendation". IMHO the semantics of this feature is indeed not very clear...

    IMHO if it's just for the CI config then it's probably better to just enrich your CI config instead.

    I'll mark this as a duplicate of #4391. Would you mind elaborating over there what problem you are trying to solve with this feature, is it the same with that of the others?

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions