*: Format with rustfmt #2188
Merged
*: Format with rustfmt #2188
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
Co-authored-by: Thomas Eizinger <[email protected]>
dvc94ch
approved these changes
Aug 9, 2021
wngr
approved these changes
Aug 9, 2021
thomaseizinger
approved these changes
Aug 9, 2021
1 task
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.
Using rustfmt across the rust-libp2p repository has been a continuous ask from contributors and the community. While using rustfmt myself, I am mostly indifferent. That said, given that most of the Rust ecosystem uses rustfmt and given that using rustfmt lowers the barrier for newcomers, this pull request formats all of rust-libp2p and adds a CI step to enforce the formatting in the future (thanks to @thomaseizinger).
I went through most of the changes. As far as I can tell, none of the pointers as comments (e.g.
some code // [1]) have been altered.