rust/tests/ui/parser/issues/issue-10392-2.rs

//@ run-rustfix

pub struct A { pub foo: isize }

fn a() -> A { panic!() }

fn main() {
    let A { .., } = a(); //~ ERROR: expected `}`
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-rustfix`
Audit uses of `span_suggestion_short` 2020-07-02 14:32:12 +09:00
			`pub struct A { pub foo: isize }`
Accept trailing commas in struct patterns We decided in the 12/10/13 weekly meeting that trailing commas should be accepted pretty much anywhere. They are currently not allowed in struct patterns, and this commit adds support for that. Closes #10392 2013-12-19 09:21:05 -08:00
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			`fn a() -> A { panic!() }`
Accept trailing commas in struct patterns We decided in the 12/10/13 weekly meeting that trailing commas should be accepted pretty much anywhere. They are currently not allowed in struct patterns, and this commit adds support for that. Closes #10392 2013-12-19 09:21:05 -08:00
			`fn main() {`
			let A { .., } = a(); //~ ERROR: expected `}`
			`}`