-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pretty printer is injecting extra newlines/spaces in funky ways in some run-fail tests #23623
Labels
A-pretty
Area: Pretty printing (including `-Z unpretty`)
Comments
I hit the same problem in a slightly different setup in #28873:
The original source for the test had no newlines before the comment in the match, but every round of pretty printing adds one. |
eddyb
added a commit
to eddyb/rust
that referenced
this issue
Oct 19, 2016
Fix some pretty printing tests Many pretty-printing tests are un-ignored. Some issues in classification of comments (trailing/isolated) and blank line counting are fixed. Some comments are printed more carefully. Some minor refactoring in pprust.rs `no-pretty-expanded` annotations are removed because this is the default now. `pretty-expanded` annotations are removed from compile-fail tests, they are not tested with pretty-printer. Closes rust-lang#23623 in favor of more specific rust-lang#37201 and rust-lang#37199 r? @nrc
eddyb
added a commit
to eddyb/rust
that referenced
this issue
Oct 19, 2016
Fix some pretty printing tests Many pretty-printing tests are un-ignored. Some issues in classification of comments (trailing/isolated) and blank line counting are fixed. Some comments are printed more carefully. Some minor refactoring in pprust.rs `no-pretty-expanded` annotations are removed because this is the default now. `pretty-expanded` annotations are removed from compile-fail tests, they are not tested with pretty-printer. Closes rust-lang#23623 in favor of more specific rust-lang#37201 and rust-lang#37199 r? @nrc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From end of the following build log:
http://buildbot.rust-lang.org/builders/auto-mac-64-opt/builds/4172/steps/test/logs/stdio
From narrowing the test down a little, it seems to be due to those tests mixing comments at the end of a statement with further multi-line comments further down.
In particular, here is my attempt to produce a more minimal test case:
Input:
Transcript of a run:
The text was updated successfully, but these errors were encountered: