minus-squarearendjr@programming.devOPtoProgramming@programming.dev•Feds: Critical Software Must Drop C/C++ by 2026 or Face Risklinkfedilinkarrow-up0·4 days agoUsing smart pointers doesn’t eliminate the memory safety issue, it merely addresses one aspect of it. Even with smart pointers, nothing is preventing you from passing references and using it them after they’re freed. linkfedilink
arendjr@programming.dev to Programming@programming.devEnglish · 4 days agoFeds: Critical Software Must Drop C/C++ by 2026 or Face Riskplus-squarethenewstack.ioexternal-linkmessage-square25fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkFeds: Critical Software Must Drop C/C++ by 2026 or Face Riskplus-squarethenewstack.ioarendjr@programming.dev to Programming@programming.devEnglish · 4 days agomessage-square25fedilink
minus-squarearendjr@programming.devtoProgramming@programming.dev•Self-documenting Codelinkfedilinkarrow-up0·14 days agoI think that’s very team/project dependent. I’ve seen it done before indeed, but I’ve never been on a team where it was considered idiomatic. linkfedilink
arendjr@programming.dev to Rust@programming.devEnglish · 2 months agoAsync Rust can be a pleasure to work with (without Send + Sync + 'static)plus-squareemschwartz.meexternal-linkmessage-square0fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkAsync Rust can be a pleasure to work with (without Send + Sync + 'static)plus-squareemschwartz.mearendjr@programming.dev to Rust@programming.devEnglish · 2 months agomessage-square0fedilink
Using smart pointers doesn’t eliminate the memory safety issue, it merely addresses one aspect of it. Even with smart pointers, nothing is preventing you from passing references and using it them after they’re freed.