[masklinn]

> You can only take a reference to an lvalue, which is (essentially) an expression that is legal to use in the form `my_lvalue = ….

I mean it could implicitly allocate, that's what Rust does for instance.

Your second and third attempts would not compile though, the first would by returning a `&'static T`.

[steveklabnik]

"implicitly allocate" is slightly misleading, imho. It's promoted to a static. There's no malloc involved.

[masklinn]

> "implicitly allocate" is slightly misleading

Maybe. I just meant that storage is created implicitly (static or stackframe depending on the case), then a reference is created to that.,

[steveklabnik]

Totally, I don't think you're wrong, just like, people read "allocate" in different ways. I wish words were clearer, heh.