rust/tests/ui/imports/glob-use-std.rs

// Issue #7580

//@ run-fail
//@ error-pattern:panic works
//@ ignore-emscripten no processes

use std::*;

fn main() {
    panic!("panic works")
}
testsuite: test for fixed issue. Closes #7580. Fixed by the privacy changes that allowed the `mod std {}` at the top level of `std` to be non-`pub`. 2013-10-20 20:17:13 +11:00			`// Issue #7580`

Move tests from `test/run-fail` to UI 2020-04-16 15:50:32 +09:00			`//@ run-fail`
Update infrastructure for fail -> panic This includes updating the language items and marking what needs to change after a snapshot. If you do not use the standard library, the language items you need to implement have changed. For example: ```rust #[lang = "fail_fmt"] fn fail_fmt() -> ! { loop {} } ``` is now ```rust #[lang = "panic_fmt"] fn panic_fmt() -> ! { loop {} } ``` Related, lesser-implemented language items `fail` and `fail_bounds_check` have become `panic` and `panic_bounds_check`, as well. These are implemented by `libcore`, so it is unlikely (though possible!) that these two renamings will affect you. [breaking-change] Fix test suite 2014-10-28 14:07:33 -04:00			`//@ error-pattern:panic works`
Skip tests on emscripten 2020-05-08 00:39:02 +09:00			`//@ ignore-emscripten no processes`
testsuite: test for fixed issue. Closes #7580. Fixed by the privacy changes that allowed the `mod std {}` at the top level of `std` to be non-`pub`. 2013-10-20 20:17:13 +11:00
			`use std::*;`

			`fn main() {`
Rename fail! to panic! https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . \| xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] 2014-10-09 15:17:22 -04:00			`panic!("panic works")`
testsuite: test for fixed issue. Closes #7580. Fixed by the privacy changes that allowed the `mod std {}` at the top level of `std` to be non-`pub`. 2013-10-20 20:17:13 +11:00			`}`