MaliciousKebab@sh.itjust.works to Programmer Humor@programming.devEnglish · 1 year agoWriting C++ is easy.sh.itjust.worksimagemessage-square86fedilinkarrow-up11.07Karrow-down120
arrow-up11.05Karrow-down1imageWriting C++ is easy.sh.itjust.worksMaliciousKebab@sh.itjust.works to Programmer Humor@programming.devEnglish · 1 year agomessage-square86fedilink
minus-squareBoinketh@lemm.eelinkfedilinkEnglisharrow-up16arrow-down1·edit-21 year agoRust has better runtime errors, too. If you run a dev build, it should pretty much never segfault unless you use unsafe and will instead tell you what went wrong and where, no valgrind necessary.
minus-squareJakeHimself@programming.devlinkfedilinkEnglisharrow-up8·1 year agoWould know, I’ve never had a runtime error in Rust /s
minus-squareeth0p@iusearchlinux.fyilinkfedilinkEnglisharrow-up3·1 year agoCan’t have a runtime error if you don’t have a compiled binary *taps forehead* (For the record, I say this as someone who enjoys Rust)
minus-squareBeanie@programming.devlinkfedilinkarrow-up1·1 year ago‘it should pretty much never segfault’ uh, isn’t that the entire point of Rust? Unless you’re counting failing a bounds check as a segfault
minus-squareBoinketh@lemm.eelinkfedilinkarrow-up1·1 year agoI’m confused by your comment. Yes, that is a major benefit of using Rust. That was my point.
Rust has better runtime errors, too. If you run a dev build, it should pretty much never segfault unless you use
unsafeand will instead tell you what went wrong and where, no valgrind necessary.Would know, I’ve never had a runtime error in Rust /s
Can’t have a runtime error if you don’t have a compiled binary *taps forehead*
(For the record, I say this as someone who enjoys Rust)
‘it should pretty much never segfault’ uh, isn’t that the entire point of Rust? Unless you’re counting failing a bounds check as a segfault
I’m confused by your comment. Yes, that is a major benefit of using Rust. That was my point.