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.
Following as much from c2rust/wiki/Release-Process as still works/applies, plus some extra additions, I ...
cargo outdated -R
: doesn't work due to unknown print requestsplit-debuginfo
cargo update
: doesn't work because of old nightlycargo clippy
:cargo clippy --fix
cargo clippy
fixescargo fmt --check
0.19.0
to0.20.0
.cargo build
cargo +stable build -p c2rust
publish = false
in crates that are unstable due to#![feature(rustc_private)]
.Then I will publish the crates in this order with
cargo +stable -p $package
:c2rust-asm-casts
c2rust-ast-builder
c2rust-ast-printer
c2rust-build-paths
c2rust-ast-exporter
c2rust-bitfields-derive
c2rust-bitfields
c2rust-transpile
c2rust
or if this works, then I'll use this:
I need to use
cargo +stable
for this because the pinned nightly does not correctly resolve theCargo.lock
for a workspace, and thus tries to incompatibly update it.