Taking address of a temporary is allowed if the function's result is consumed...

Lifetime of temporary to which a local reference is bound in a c++ coroutine...

c++ warning about indirectly taking reference to temporary...

Why const reference could not extend lifetime of temporary...

Returning temporary object and binding to const reference...

Ternary operator and prolonging the lifetime of a temporary object via reference-to-const...

Does the compiler perform return value optimisation in case of returning member variable?...

Possible run-time problems arising from moving temporary object to a heap allocated object?...

Lifetime extension of temporary container's element...

Why do const references extend the lifetime of rvalues?...

Why does "return string(...)" return a reference to a temporary?...

warning: returning reference to temporary...

Lambda capturing rvalue reference by reference...

Is it false positive here: warning C4172: returning address of local variable or temporary?...

Are function parameter objects temporary objects?...

Is this access to temporary safe according to the C++ standard?...

Why I don’t have to free string from c_str function of std::string?...

Can you bind a const T*&& to an xvalue of type T*?...

What do braces on the left-hand side of a variable declaration mean, such as in T {x} = y?...

Why is a temporary std::lock_guard object immediately unlocked?...

Why does this work: returning C string literal from std::string function and calling c_str()...

Initialize polymorphic C array with references/pointers to temporary statically allocated objects in...

When are temporary objects destroyed?...

What is the lifetime of temporary function arguments?...

Is it safe to use the std::string::c_str() of a temporary string?...

Unexpected result when storing c_str() of temporary std::string in a variable...

How to prevent temporary materialization for const reference parameters...

When binding a const reference to a temporary object, why is the destructor called twice?...

const reference to temporary oddity...

Does std::string {} = "hi"; induce temporary materialization?...