reynmorris

5 ms·

1. 1.▲
   by reynmorris 2y ago

   You can assume that the collection doesn't have good coverage, but what I'm saying is the constructs in the C++ language are there to make it have good coverage. Pair this with some Clang sanitation (like banning raw pointers) and
2. 2.▲
   by reynmorris 2y ago

   That is not an issue with the safety of the Vector, it is an issue with the safety of 'int' and raw pointers. If the Vector grows, that pointer points to freed memory. But yes, in my implementation I have a safe version of int cal
3. 3.▲
   by reynmorris 2y ago

   It's simple, whether the backing memory is heap or stack, it's bounds checked. And overriding all the operators and only returning safe types prevents many types of undefined behavior. Of course you can fuck with it enough to make
4. 4.▲
   by reynmorris 2y ago

   A lot of coders already do this. My STL replacement has Vector and VectorUnsafe. Vector is checked to the hilt for bounds safety, stack safety, UB safety, etc. and is slower. But if I have a tight loop, I can use VectorUnsafe and just make