Set --errors-as-warnings by default
#430
Merged
Conversation
This file contains 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
Nadrieril
force-pushed
the
errors-as-warnings-by-default
branch
from
250f33b
to
32d5241
Compare
Nadrieril
force-pushed
the
errors-as-warnings-by-default
branch
from
32d5241
to
c3d8058
Compare
|
cc @EschericHya @sonmarcho @msprotz this changes the default behavior of charon to not fail when there are errors. |
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.
This way charon passes on a lot more crates right away. We now have
--error-on-warningsas a new flag that restores the old behavior.This should drastically change the behavior on the rustc test suite (#145).
Fixes #416.