rust/tests/ui/error-codes/E0609-private-method.stderr

error[E0609]: no field `method` on type `Foo`
  --> $DIR/E0609-private-method.rs:15:7
   |
LL |     f.method;
   |       ^^^^^^ unknown field

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0609`.
Don't suggest adding parentheses to call an inaccessible method. Previously, the test code would emit E0615, thus revealing the existence of private methods that the programmer probably does not care about. Now it ignores their existence instead, producing error E0609 (no field). The motivating example is: ```rust let x = std::rc::Rc::new(()); x.inner; ``` which would previously mention the private method `Rc::inner()`, even though `Rc<T>` intentionally has no public methods so that it can be a transparent smart pointer for any `T`. 2023-08-29 15:41:33 -05:00			error[E0609]: no field `method` on type `Foo`
			`--> $DIR/E0609-private-method.rs:15:7`
			`\|`
			`LL \| f.method;`
			`\| ^^^^^^ unknown field`

Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Don't suggest adding parentheses to call an inaccessible method. Previously, the test code would emit E0615, thus revealing the existence of private methods that the programmer probably does not care about. Now it ignores their existence instead, producing error E0609 (no field). The motivating example is: ```rust let x = std::rc::Rc::new(()); x.inner; ``` which would previously mention the private method `Rc::inner()`, even though `Rc<T>` intentionally has no public methods so that it can be a transparent smart pointer for any `T`. 2023-08-29 15:41:33 -05:00
			For more information about this error, try `rustc --explain E0609`.