rust/tests/ui/issues/issue-25386.stderr

error[E0616]: field `c_object` of struct `Item` is private
  --> $DIR/issue-25386.rs:19:16
   |
LL |         (*$var.c_object).$member.is_some()
   |                ^^^^^^^^ private field
...
LL |     println!("{}", check_ptr_exist!(item, name));
   |                    ---------------------------- in this macro invocation
   |
   = note: this error originates in the macro `check_ptr_exist` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0616`.
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			error[E0616]: field `c_object` of struct `Item` is private
Add span label to primary error span 2020-03-22 18:18:06 +00:00			`--> $DIR/issue-25386.rs:19:16`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
			`LL \| (*$var.c_object).$member.is_some()`
Add span label to primary error span 2020-03-22 18:18:06 +00:00			`\| ^^^^^^^^ private field`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`...`
			`LL \| println!("{}", check_ptr_exist!(item, name));`
			`\| ---------------------------- in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 13:56:47 +00:00			`\|`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 19:52:25 +00:00			= note: this error originates in the macro `check_ptr_exist` (in Nightly builds, run with -Z macro-backtrace for more info)
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			For more information about this error, try `rustc --explain E0616`.