Have You Heard of Provenance?
summary
Explains why C/C++ pointer provenance matters by showing a real clang-tidy warning performance-no-int-to-ptr and a concrete example: casting adjacent objects to integers and back (a pointer-to-integer round trip) can appear to produce a valid pointer to the neighbor but actually interacts with the past-the-end pointer rule and abstract-machine provenance rules, letting optimizations treat values as integers and create undefined behavior; conclusion: ptr→int casts have provenance side effects that compilers may exploit.
AI-written summary · about
related talks
01h 39m“Learning and Teaching Modern C++”
20mTouring the Tips of the Week Series
01h 02m“How to Write Effective Documentation for C++ Libraries..."
01h 02mNaming is Hard: Let's Do Better
01h 15mDocumentation in the Era of Concepts and Ranges
06mIf You Build It, Will They Come?
36mWriting Valuable Papers
07mTooling and Sharing Traceability Discussion