Reintroduce box syntax where needed
Otherwise, this line is a lie.
This commit is contained in:
parent
cf636c233d
commit
5ce1b33502
@ -687,7 +687,9 @@ than the hundred `int`s that make up the `BigStruct`.
|
|||||||
|
|
||||||
This is an antipattern in Rust. Instead, write this:
|
This is an antipattern in Rust. Instead, write this:
|
||||||
|
|
||||||
```{rust}
|
```rust
|
||||||
|
#![feature(box_syntax)]
|
||||||
|
|
||||||
struct BigStruct {
|
struct BigStruct {
|
||||||
one: i32,
|
one: i32,
|
||||||
two: i32,
|
two: i32,
|
||||||
@ -706,10 +708,13 @@ fn main() {
|
|||||||
one_hundred: 100,
|
one_hundred: 100,
|
||||||
});
|
});
|
||||||
|
|
||||||
let y = Box::new(foo(x));
|
let y = box foo(x);
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Note that this uses the `box_syntax` feature gate, so this syntax may change in
|
||||||
|
the future.
|
||||||
|
|
||||||
This gives you flexibility without sacrificing performance.
|
This gives you flexibility without sacrificing performance.
|
||||||
|
|
||||||
You may think that this gives us terrible performance: return a value and then
|
You may think that this gives us terrible performance: return a value and then
|
||||||
|
Loading…
x
Reference in New Issue
Block a user