|
|
|
|
|
by masklinn
1756 days ago
|
|
> In modern C++ you write with no controlling memory allocation at all and you dont write your own arrays with can be overflown. The simplest and most straightforward way to access an std::vector item allows OOB read. Literally every smart pointer an be empty and will UB with no warning if deref'd in that state (that includes the brand new std::optional). The rules of X remain a tarpit lined with shit-smeared stakes, Chrome got bit by a GDI leak just a pair of years back because of that (a refactoring in an RAII object removed an operator= overload and started leaking GDI handles by the hundred when using chrome remote desktop). |
|