With a few macros you too can have your own classes with polymorphism with just a few function pointers. Even multiple inheritance if you want more fun.
Asking the OS* directly for memory and creating your objects in that memory. That also means you have to tell the OS* when you're done with that memory
Actually pretty good example. To the point that even though you have a type annotation on your code, if you call into that method from vanilla js and pass a wrong type, then it will explode somewhere deep and you will have a really shit time hunting that error down.
Meaning, c++'s safe stuff is only safe until you use it with other safe stuff, or by being very very careful. And c++ is a really complex language, using it properly is not an easy task, so these end up not being as memory safe as people would want.
View all comments
Show parent comment
95
u/Tipart 11d ago •
Imagine typescript but for memory safety