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

use std::any::Any;
fn main()
{
    fn bar(x:i32) ->i32 { 3*x };
    let b:Box<dyn Any> = Box::new(bar as fn(_)->_);
    b.downcast_ref::<fn(_)->_>(); //~ ERROR E0282
}
Split up tests, reduce coverage 2015-04-24 12:34:27 -06:00			`use std::any::Any;`
			`fn main()`
			`{`
			`fn bar(x:i32) ->i32 { 3*x };`
Update ui test suite to use dyn 2019-05-28 14:46:13 -04:00			`let b:Box<dyn Any> = Box::new(bar as fn(_)->_);`
Make RFC 1214 warnings into errors, and rip out the "warn or err" associated machinery. Future such attempts should go through lints anyhow. There is a fair amount of fallout in the compile-fail tests, as WF checking now occurs earlier in the process. 2015-12-15 04:31:58 -05:00			`b.downcast_ref::<fn(_)->_>(); //~ ERROR E0282`
Delay specific span_bug() call until abort_if_errors() An actual typeck error is the cause of many failed compilations but an unrelated bug is being reported instead. It is triggered because a typeck error is presumably not yet identified during compiler execution, which would normally bypass an invariant in the presence of other errors. In this particular situation, we delay the reporting of the bug until abort_if_errors(). Closes #23827, closes #24356, closes #23041, closes #22897, closes #23966, closes #24013, and closes #23729 2015-04-13 01:13:09 -06:00			`}`