rust/src/test/ui/cancel-clean-via-immediate-rvalue-ref.rs

// run-pass
// pretty-expanded FIXME #23616

#![feature(box_syntax)]

fn foo(x: &mut Box<u8>) {
    *x = box 5;
}

pub fn main() {
    foo(&mut box 4);
}
tests: Add missing run-pass annotations 2019-07-27 00:54:25 +03:00			`// run-pass`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 13:13:15 -07:00			`// pretty-expanded FIXME #23616`

fallout: run-pass tests that use box. (many could be ported to `Box::new` instead in the future.) 2015-01-08 02:25:56 +01:00			`#![feature(box_syntax)]`
librustc: Remove `~EXPR`, `~TYPE`, and `~PAT` from the language, except for `~str`/`~[]`. Note that `~self` still remains, since I forgot to add support for `Box<self>` before the snapshot. How to update your code: * Instead of `~EXPR`, you should write `box EXPR`. * Instead of `~TYPE`, you should write `Box<Type>`. * Instead of `~PATTERN`, you should write `box PATTERN`. [breaking-change] 2014-05-05 18:56:44 -07:00
			`fn foo(x: &mut Box<u8>) {`
			`*x = box 5;`
partially fix immediate rvalues The code generation previously assumed a reference could not alter the value in a way the destructor would notice. This is an incorrect assumption for `&mut`, and is also incorrect for an `&` pointer to a non-`Freeze` type. Closes #7972 2013-10-17 03:43:22 -04:00			`}`

			`pub fn main() {`
librustc: Remove `~EXPR`, `~TYPE`, and `~PAT` from the language, except for `~str`/`~[]`. Note that `~self` still remains, since I forgot to add support for `Box<self>` before the snapshot. How to update your code: * Instead of `~EXPR`, you should write `box EXPR`. * Instead of `~TYPE`, you should write `Box<Type>`. * Instead of `~PATTERN`, you should write `box PATTERN`. [breaking-change] 2014-05-05 18:56:44 -07:00			`foo(&mut box 4);`
partially fix immediate rvalues The code generation previously assumed a reference could not alter the value in a way the destructor would notice. This is an incorrect assumption for `&mut`, and is also incorrect for an `&` pointer to a non-`Freeze` type. Closes #7972 2013-10-17 03:43:22 -04:00			`}`