cqst [she/her]@lemmy.blahaj.zone to linuxmemes@lemmy.worldEnglish · 2 days agothe perfect browserlemmy.blahaj.zoneimagemessage-square172fedilinkarrow-up1654arrow-down132
arrow-up1622arrow-down1imagethe perfect browserlemmy.blahaj.zonecqst [she/her]@lemmy.blahaj.zone to linuxmemes@lemmy.worldEnglish · 2 days agomessage-square172fedilink
minus-squaredreugeworst@lemmy.mllinkfedilinkarrow-up1·1 day agoWhich language would you say is not memory safe then? Is there any serious language out there where you should expect memory issues if you don’t make any mistakes?
minus-squareZacryon@feddit.orglinkfedilinkarrow-up1·2 minutes agoNo. I changed my mind just very recently throughout this discussion. I agree now that the lack of enforcement of memory safe techniques in C++ makes it inherently memory-unsafe. That doesn’t change the fact though that it’s possible to write memory safe code, if you know what you’re doing, use the right patterns, classes etc…
Which language would you say is not memory safe then? Is there any serious language out there where you should expect memory issues if you don’t make any mistakes?
No. I changed my mind just very recently throughout this discussion.
I agree now that the lack of enforcement of memory safe techniques in C++ makes it inherently memory-unsafe.
That doesn’t change the fact though that it’s possible to write memory safe code, if you know what you’re doing, use the right patterns, classes etc…