@MaliciousKebab@sh.itjust.works to Programmer Humor@programming.devEnglish • 2 years agoWriting C++ is easy.sh.itjust.worksimagemessage-square85fedilinkarrow-up11.08Karrow-down120
arrow-up11.06Karrow-down1imageWriting C++ is easy.sh.itjust.works@MaliciousKebab@sh.itjust.works to Programmer Humor@programming.devEnglish • 2 years agomessage-square85fedilink
minus-square@JakeHimself@programming.devlinkfedilinkEnglish8•2 years agoWould know, I’ve never had a runtime error in Rust /s
minus-square@eth0p@iusearchlinux.fyilinkfedilinkEnglish3•2 years 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-square@asdfasdfasdf@lemmy.worldlinkfedilink1•2 years agoThis is actually unironically a major benefit of Rust - compile time errors are supposed to be for dev mistakes and runtime errors supposed to be for user mistakes. Way easier to debug something at compile time instead of runtime.
minus-square@Beanie@programming.devlinkfedilink1•2 years 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
deleted by creator
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)
This is actually unironically a major benefit of Rust - compile time errors are supposed to be for dev mistakes and runtime errors supposed to be for user mistakes. Way easier to debug something at compile time instead of runtime.
‘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
deleted by creator