rust/src/test/ui/issue-19100.stderr

warning[E0170]: pattern binding `Bar` is named the same as one of the variants of the type `Foo`
  --> $DIR/issue-19100.rs:27:1
   |
27 | Bar if true
   | ^^^
   |
   = help: if you meant to match on a variant, consider making the path in the pattern qualified: `Foo::Bar`

warning[E0170]: pattern binding `Baz` is named the same as one of the variants of the type `Foo`
  --> $DIR/issue-19100.rs:32:1
   |
32 | Baz if false
   | ^^^
   |
   = help: if you meant to match on a variant, consider making the path in the pattern qualified: `Foo::Baz`
Introduce 'run-pass' header to 'ui' tests in compiletest. Fix issue #36516. The 'run-pass' header cause a 'ui' test to execute the result. It is used to test the lint output, at the same time ensure those lints won't cause the source code to become compile-fail. 12 run-pass/run-pass-fulldeps tests gained the header and are moved to ui/ui-fulldeps. After this move, no run-pass/run-pass-fulldeps tests should rely on the compiler's JSON message. This allows us to stop passing `--error-format json` in run-pass tests, thus fixing #36516. 2017-05-13 04:54:50 -05:00			warning[E0170]: pattern binding `Bar` is named the same as one of the variants of the type `Foo`
			`--> $DIR/issue-19100.rs:27:1`
			`\|`
			`27 \| Bar if true`
			`\| ^^^`
			`\|`
			= help: if you meant to match on a variant, consider making the path in the pattern qualified: `Foo::Bar`

			warning[E0170]: pattern binding `Baz` is named the same as one of the variants of the type `Foo`
			`--> $DIR/issue-19100.rs:32:1`
			`\|`
			`32 \| Baz if false`
			`\| ^^^`
			`\|`
			= help: if you meant to match on a variant, consider making the path in the pattern qualified: `Foo::Baz`