Remove --debug-build, add --cargo-profile instead
#218
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sharkdp
commented
Oct 15, 2025
AlexWaygood
approved these changes
Oct 15, 2025
sharkdp
force-pushed
the
cargo-profile-option
branch
from
515245c to
cdc027f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
--debug-buildoption and add a--cargo-profileoption instead. This allows for more flexibility (--cargo-profile devcorresponds to--debug-build)build.target-dirsetting by explicitly specifying the target-dir (same as for ty)python-interpreter-pathfor pyrefly runs (apparently, the name of the option has changed recently)I tested this for both ty and pyrefly with different cargo profiles.