rust/tests/ui/issues/issue-1920-3.rs

//! Test that when a crate is linked multiple times that the shortest absolute path name is used

// aux-build:issue-1920.rs

mod foo {
    pub extern crate issue_1920;
}

extern crate issue_1920;

fn assert_clone<T>() where T : Clone { }

fn main() {
    assert_clone::<foo::issue_1920::S>();
    //~^ ERROR `S: Clone` is not satisfied
}
Fix and add tests regarding extern crate paths 2015-08-01 19:41:01 +02:00			`//! Test that when a crate is linked multiple times that the shortest absolute path name is used`

Moved and renamed ui issue tests. 2018-11-05 04:00:03 +00:00			`// aux-build:issue-1920.rs`
Followup for #46112. Sorting by crate-num should ensure that we favor `std::foo::bar` over `any_other_crate::foo::bar`. Interestingly, this change had a much larger impact on our internal test suite than PR #46708 (which was my original fix to #46112). 2017-12-19 15:04:02 +01:00
Fix and add tests regarding extern crate paths 2015-08-01 19:41:01 +02:00			`mod foo {`
Followup for #46112. Sorting by crate-num should ensure that we favor `std::foo::bar` over `any_other_crate::foo::bar`. Interestingly, this change had a much larger impact on our internal test suite than PR #46708 (which was my original fix to #46112). 2017-12-19 15:04:02 +01:00			`pub extern crate issue_1920;`
Fix and add tests regarding extern crate paths 2015-08-01 19:41:01 +02:00			`}`

Followup for #46112. Sorting by crate-num should ensure that we favor `std::foo::bar` over `any_other_crate::foo::bar`. Interestingly, this change had a much larger impact on our internal test suite than PR #46708 (which was my original fix to #46112). 2017-12-19 15:04:02 +01:00			`extern crate issue_1920;`
Fix and add tests regarding extern crate paths 2015-08-01 19:41:01 +02:00
			`fn assert_clone<T>() where T : Clone { }`

			`fn main() {`
Followup for #46112. Sorting by crate-num should ensure that we favor `std::foo::bar` over `any_other_crate::foo::bar`. Interestingly, this change had a much larger impact on our internal test suite than PR #46708 (which was my original fix to #46112). 2017-12-19 15:04:02 +01:00			`assert_clone::<foo::issue_1920::S>();`
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 10:40:56 +03:00			//~^ ERROR `S: Clone` is not satisfied
core: Shuffle around float parsing Stop using stability to hide the implementation details of ParseFloatError and instead move the error type into the `dec2flt` module. Also move the implementation blocks of `FromStr for f{32,64}` into `dec2flt` directly. 2015-08-17 14:16:41 -07:00			`}`