Lightning Talk: Ref, C++ const ref, immutable ref?
summary
Claims that const reference is read-only view but still points at mutable data and can be changed through globals or const_cast; shows repeated compare checks as concrete evidence. Compares three approaches: copying values (costly), using restrict keyword (breaks when passing elsewhere), and an immutable class makes members const (prevents const_cast but forces lifelong constness). Presents an immutable_ref idea as a proposed type; immutable class is implemented and works but proves inflexible, immutable_ref remains a sketch.
AI-written summary · about
related talks
01h 03mRefactoring to Immutability
01h 02mBack to Basics: Forwarding References - How to Forward Parameters in Modern C++
06mLightning Talk: Fun with Pointers to Members
01h 02mUniversal/Forwarding References
27mLightning Talks - Day 1
01h 01mBack to Basics: Concepts in C++
07mOn parameter sinks
07mLightning Talk: Higher-Order Template Metaprogramming with C++23