-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make the "detect-old-time" UI test more representative
The test code did have an inference failure, but that would have failed on Rust 1.79 and earlier too. Now it is rewritten to be specifically affected by 1.80's `impl FromIterator<_> for Box<str>`.
- Loading branch information
Showing
2 changed files
with
16 additions
and
8 deletions.
There are no files selected for viewing
13 changes: 9 additions & 4 deletions
13
tests/ui/inference/detect-old-time-version-format_description-parse.rs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,13 @@ | ||
#![crate_name = "time"] | ||
#![crate_type = "lib"] | ||
|
||
fn main() { | ||
let items = Box::new(vec![]); //~ ERROR E0282 | ||
// This code compiled without error in Rust 1.79, but started failing in 1.80 | ||
// after the addition of several `impl FromIterator<_> for Box<str>`. | ||
|
||
pub fn parse() -> Option<Vec<()>> { | ||
let iter = std::iter::once(Some(())).map(|o| o.map(Into::into)); | ||
let items = iter.collect::<Option<Box<_>>>()?; //~ ERROR E0282 | ||
//~^ NOTE this is an inference error on crate `time` caused by an API change in Rust 1.80.0; update `time` to version `>=0.3.35` | ||
Some(items.into()) | ||
//~^ NOTE type must be known at this point | ||
//~| NOTE this is an inference error on crate `time` caused by an API change in Rust 1.80.0; update `time` to version `>=0.3.35` | ||
items.into(); | ||
} |
11 changes: 7 additions & 4 deletions
11
tests/ui/inference/detect-old-time-version-format_description-parse.stderr
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters