Question about dangling references caused by returning const& parameter as const&

[denzor200]

In C++ the functionality of references gives us one well-known way to shoot yourself in the foot, whereas using the pointers such foot-shooting was impossible.

const int& identity(const int& val) {
    return val;
}

void sample() {
    const int& val = identity(int(10)); // UB - val is a dangling reference
    const int val2 = identity(int(10)); // OK
    const int& val3 = identity(val2);   // OK
}

Will guidelines protect us from this kind of lifetime-related problem?

[bgloyer]

Probably the closest is:

F.43: Never (directly or indirectly) return a pointer or a reference to a local object