Generated build.rs: Exempt from rustfmt #57
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
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.
The board.rs generated by this is regularly reformatted by
cargo fmt. Yes, CI knows to work around this by using--config format_generated_files=false, but users do iscargo fmt, and if some exception is not in those defaults, at least I always wind up with diffs in my checkout.The
@generatedis removed because apparently something injects this anyway. The explicit module-level comment is added to allow actually finding what generated this (because it took me a bit to look it up). No version information is placed in there because that'd be a source of constant churn.