rust/tests/ui/panics/panic-task-name-none.rs

//@ run-fail
//@ error-pattern:thread '<unnamed>' panicked
//@ error-pattern:test
//@ needs-threads

use std::thread;

fn main() {
    let r: Result<(), _> = thread::spawn(move || {
                               panic!("test");
                           })
                               .join();
    assert!(r.is_ok());
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-fail`
			`//@ error-pattern:thread '<unnamed>' panicked`
			`//@ error-pattern:test`
compiletest: Add a `//@ needs-threads` directive This commit is extracted from #122036 and adds a new directive to the `compiletest` test runner, `//@ needs-threads`. This is intended to capture the need that a target must implement threading to execute a specific test, typically one that uses `std::thread`. This is primarily done for WebAssembly targets which currently do not have threads by default. This enables transitioning a lot of `//@ ignore-wasm*`-style ignores into a more self-documenting `//@ needs-threads` directive. Additionally the `wasm32-wasi-preview1-threads` target, for example, does actually have threads, but isn't tested in CI at this time. This change enables running these tests for that target, but not other wasm targets. 2024-03-06 12:19:20 -08:00			`//@ needs-threads`
Make a task name use a `SendStr`, allowing for either static or owned strings 2013-10-05 21:01:58 +02:00
Fallout from stabilization 2015-02-17 15:10:25 -08:00			`use std::thread;`
Remove linked failure from the runtime The reasons for doing this are: * The model on which linked failure is based is inherently complex * The implementation is also very complex, and there are few remaining who fully understand the implementation * There are existing race conditions in the core context switching function of the scheduler, and possibly others. * It's unclear whether this model of linked failure maps well to a 1:1 threading model Linked failure is often a desired aspect of tasks, but we would like to take a much more conservative approach in re-implementing linked failure if at all. Closes #8674 Closes #8318 Closes #8863 2013-11-21 16:55:40 -08:00
Make a task name use a `SendStr`, allowing for either static or owned strings 2013-10-05 21:01:58 +02:00			`fn main() {`
run rustfmt on test/run-fail folder 2016-05-27 08:09:36 +05:30			`let r: Result<(), _> = thread::spawn(move \|\| {`
			`panic!("test");`
			`})`
			`.join();`
librustc: Match trait self types exactly. This can break code that looked like: impl Foo for Box<Any> { fn f(&self) { ... } } let x: Box<Any + Send> = ...; x.f(); Change such code to: impl Foo for Box<Any> { fn f(&self) { ... } } let x: Box<Any> = ...; x.f(); That is, upcast before calling methods. This is a conservative solution to #5781. A more proper treatment (see the xfail'd `trait-contravariant-self.rs`) would take variance into account. This change fixes the soundness hole. Some library changes had to be made to make this work. In particular, `Box<Any>` is no longer showable, and only `Box<Any+Send>` is showable. Eventually, this restriction can be lifted; for now, it does not prove too onerous, because `Any` is only used for propagating the result of task failure. This patch also adds a test for the variance inference work in #12828, which accidentally landed as part of DST. Closes #5781. [breaking-change] 2014-06-25 18:18:13 -07:00			`assert!(r.is_ok());`
Make a task name use a `SendStr`, allowing for either static or owned strings 2013-10-05 21:01:58 +02:00			`}`