Re:Show HN: Drogon – A C++14/17 based high performance HTTP ...
by dearrifling on Tuesday March 19, 2019 @01:37AM
(#19428350)
That has nothing to do with memory safety, that's just plain UB.
[ Parent
| on HN ]
Re:Show HN: Drogon – A C++14/17 based high performance HTTP ...
by Thorrez on Tuesday March 19, 2019 @01:54AM
(#19428417)
According to the spec, it can lead to all the same problems that any UB leads to, including all the problems that any memory unsafety leads to. The code is allowed by the spec to cause memory unsafety.
But to list some direct memory unsafety possibilities: indexing off the end of an array, indexing off the end of a vector, dereferencing a bad pointer, dereferencing a null pointer, dereferencing a bad iterator, double delete.