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

struct P { child: Option<Box<P>> }
trait PTrait {
   fn getChildOption(&self) -> Option<Box<P>>;
}

impl PTrait for P {
   fn getChildOption(&self) -> Option<Box<P>> {
       static childVal: Box<P> = self.child.get();
       //~^ ERROR attempt to use a non-constant value in a constant
       panic!();
   }
}

fn main() {}
tests: remove uses of Gc. 2014-10-02 08:10:09 +03:00			`struct P { child: Option<Box<P>> }`
Make moves explicit in doc examples Had to remove the buffalo example. It was awkward to update for explicit moves. 2012-09-18 22:33:49 -07:00			`trait PTrait {`
tests: remove uses of Gc. 2014-10-02 08:10:09 +03:00			`fn getChildOption(&self) -> Option<Box<P>>;`
Make moves explicit in doc examples Had to remove the buffalo example. It was awkward to update for explicit moves. 2012-09-18 22:33:49 -07:00			`}`

librustc: Replace `impl Type : Trait` with `impl Trait for Type`. rs=implflipping 2013-02-14 11:47:00 -08:00			`impl PTrait for P {`
tests: remove uses of Gc. 2014-10-02 08:10:09 +03:00			`fn getChildOption(&self) -> Option<Box<P>> {`
			`static childVal: Box<P> = self.child.get();`
Resolve incorrect diagnostic for using a non-const value in a constant 2019-02-07 16:03:12 +01:00			`//~^ ERROR attempt to use a non-constant value in a constant`
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!();`
Make moves explicit in doc examples Had to remove the buffalo example. It was awkward to update for explicit moves. 2012-09-18 22:33:49 -07:00			`}`
			`}`

			`fn main() {}`