Rustfmt #16
Closed
Rustfmt #16
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
|
Let's only run |
|
Also we need to only do this after #11 to avoid conflicts with that |
Closed
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.
Builds on top of #15. To see what changed since #15 see https://github.com/tillarnold/prusti-dev/compare/till_rebuilt_3..tillarnold:prusti-dev:rustfmt
Run rustfmt on the entire project.
I did this by running
cargo fmtin the repo root as well as inprusti-contractsas that appears to be a different workspace. Running./x.py fmt-allresulted in an error. Old prusti recently merged a PR that changed how the formatting inx.pyworks viperproject#1456. Maybe that fix could be relevant here too?