/explore
|
You are here 
|
abseil.io | ||
| | | | |
herbsutter.com
C++ "move" semantics are simple, and unchanged since C++11. But they are still widely misunderstood, sometimes because of unclear teaching and sometimes because of a desire to view move as something else instead of what it is. This post is an attempt to shed light on that situation. Thank you to the following for their... |
|
| | | | | ||
| | | | |
google.github.io
|
|
| | | | | ||
| | | | |
borretti.me
A survey of type systems for memory safety. |
|
| | | | | ||
| | | | |
www.yodaiken.com
[AI summary] The author outlines three technical proposals for the C standard working group to clarify undefined behavior, improve aliasing rules for memory allocators, and restrict optimizations that violate language semantics. |
|
| | | |||
