rust/tests/ui/issues/issue-54062.rs

use std::sync::Mutex;

struct Test {
    comps: Mutex<String>,
}

fn main() {}

fn testing(test: Test) {
    let _ = test.comps.inner.try_lock();
    //~^ ERROR: field `inner` of struct `Mutex` is private
}
Add test for issue-54062 2019-07-26 08:39:58 +00:00			`use std::sync::Mutex;`

			`struct Test {`
			`comps: Mutex<String>,`
			`}`

			`fn main() {}`

			`fn testing(test: Test) {`
Fix ui test. This test checks if the compiler complains about accesing a private field before complaining (or crashing) about the private function on it not marked as stable/unstable. The interface of the internal type (sys_common's Mutex) used for this was changed. With this change, it uses another function to test for the same issue. 2020-09-24 15:11:16 +00:00			`let _ = test.comps.inner.try_lock();`
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: field `inner` of struct `Mutex` is private
Add test for issue-54062 2019-07-26 08:39:58 +00:00			`}`