rust/tests/ui/array-slice-vec/vec-macro-rvalue-scope.rs

//@ run-pass


fn one() -> i32 { 1 }

// Make sure the vec![...] macro doesn't introduce hidden rvalue
// scopes (such as blocks) around the element expressions.
pub fn main() {
    assert_eq!(vec![&one(), &one(), &2], vec![&1, &1, &(one()+one())]);
    assert_eq!(vec![&one(); 2], vec![&1, &one()]);
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 12:18:55 +00:00
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 20:13:15 +00:00
Improve the vec![...] macro with UFCS. There are two limitations to the macro that this addresses: 1. the expected type is not propagated, coercions don't trigger 2. references inside element expressions don't outlive the `Vec` Both of these limitations are caused by the block in the macro expansion, previously needed to trigger a coercion from `Box<[T; N]>` to `Box<[T]>`, now possible with UFCS. 2015-01-18 11:13:23 +00:00			`fn one() -> i32 { 1 }`

			`// Make sure the vec![...] macro doesn't introduce hidden rvalue`
			`// scopes (such as blocks) around the element expressions.`
			`pub fn main() {`
			`assert_eq!(vec![&one(), &one(), &2], vec![&1, &1, &(one()+one())]);`
			`assert_eq!(vec![&one(); 2], vec![&1, &one()]);`
			`}`