Re: [Dwarf-Discuss] Inconsistency of C++ member function qualifiers

2021-10-05 Thread David Blaikie via Dwarf-Discuss
unctor is mutable or not. (so "std::any_invocable" is only callable when the object is non-const, but "std::any_invocable" is callable even on if it's a const object) > --paulr > > > > *From:* Dwarf-Discuss *On > Behalf Of *David Blaikie via Dwarf-D

Re: [Dwarf-Discuss] Inconsistency of C++ member function qualifiers

2021-10-05 Thread Paul Robinson via Dwarf-Discuss
. --paulr From: Dwarf-Discuss On Behalf Of David Blaikie via Dwarf-Discuss Sent: Tuesday, October 5, 2021 3:12 PM To: DWARF Discuss Subject: [Dwarf-Discuss] Inconsistency of C++ member function qualifiers C++ member functions can be qualified in a number of ways - classic CV (const and volatile

[Dwarf-Discuss] Inconsistency of C++ member function qualifiers

2021-10-05 Thread David Blaikie via Dwarf-Discuss
C++ member functions can be qualified in a number of ways - classic CV (const and volatile) qualifiers, and since C++11, lvalue (&) and rvalue (&&) reference qualifiers. Details here: https://en.cppreference.com/w/cpp/language/member_functions A note on 5.10, page 127 says: "C++ const-volatile qu