@@ -113,20 +113,6 @@ The directives for pretty-printing tests are:
113113 expanded output to type check it. This is needed for a pretty-mode that does
114114 not expand to valid Rust, or for other situations where the expanded output
115115 cannot be compiled.
116- - ` pretty-expanded ` allows a pretty test to also check that the expanded output
117- can be type checked. That is, after the steps above, it does two more steps:
118- 119- > 5 . Run ` rustc -Zunpretty=expanded ` on the original source
120- > 6 . Run ` rustc -Zno-codegen ` on the expanded output to make sure that it can type check
121-
122- This is needed because not all code can be compiled after being expanded.
123- Pretty tests should specify this if they can. An example where this cannot be
124- used is if the test includes ` println! ` . That macro expands to reference
125- private internal functions of the standard library that cannot be called
126- directly without the ` fmt_internals ` feature gate.
127- 128- More history about this may be found in
129- [ #23616 ] ( https://github.com/rust-lang/rust/issues/23616#issuecomment-484999901 ) .
130116- ` pp-exact ` is used to ensure a pretty-print test results in specific output.
131117 If specified without a value, then it means the pretty-print output should
132118 match the original source. If specified with a value, as in `//@
0 commit comments