Fixes to rust-toolchain.toml
handling
#1225
Merged
+9
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a few aspects of the
rust-toolchain.toml
handling, to make it easier to make future changes such as limiting the use ofrust-toolchain.toml
to the tools that use rustc internals.Fix a few obsolete references to
rust-toolchain
rather thanrust-toolchain.toml
, since c2rust doesn't use the former.Use the
rustfmt
component rather thanrustfmt-preview
, since the latter is obsolete (rustfmt has not been a "preview" for a long time).Finally, make
c2rust-transpile
use a separate file for the generatedrust-toolchain.toml
. When c2rust-transpile translates C variadics, it generates code using the (currently) nightly-only featurec_variadics
, so it emits arust-toolchain.toml
file to use nightly. Rather than copy this filefrom the
rust-toolchain.toml
used to build c2rust itself, use a separate file.This also means the generated
rust-toolchain.toml
can stop requiring toolchain components that the generated code doesn't need, such as rustc-dev. (It still requiresrustfmt
, as c2rust may runcargo fmt
on the generated code if invokingc2rust-refactor
.)