so… i hadn’t been using `cargo check` (`./cargo ch...
# development
w
so… i hadn’t been using
cargo check
(
./cargo check
in pantsbuild/pants) for iteration on the rust code. and, um. i should have been
h
That was a huge motivation for adding the
./cargo
script
w
much faster than
MODE=debug
.
i’ll add a blurb to the docsite.
h
Ohhh, now that we don’t need to install any Rust tools, we might be able to get rid of
./cargo
once I finish this global install change. Tbd
w
yea
i guess https://www.pantsbuild.org/v2.2/docs/contributions-rust already described this, but i made some clarifying edits. not sure how to view page history
👍 1
h
not sure how to view page history
in the admin view, on the right hand side there’s a “view history” menu item iirc
👍 1
Ohhh, now that we don’t need to install any Rust tools, we might be able to get rid of ./cargo once I finish this global install change.
Very cool. The script will only be this:
Copy code
if ! command -v rustup &> /dev/null; then
  die "Please install Rustup and ensure \`rustup\` is on your PATH (usually by adding ~/.cargo/bin). See <https://rustup.rs>."
fi

cd "${REPO_ROOT}/src/rust/engine" || exit "${PIPESTATUS[0]}"
exec cargo "$@"
w
🤘