𝔻𝔼𝕍𝕀𝕃𝕀𝕊ℍ@lemmy.world to Programmer Humor@lemmy.ml · 2 years agoC++ Momentlemmy.worldimagemessage-square152fedilinkarrow-up11.04Karrow-down132
arrow-up11.01Karrow-down1imageC++ Momentlemmy.world𝔻𝔼𝕍𝕀𝕃𝕀𝕊ℍ@lemmy.world to Programmer Humor@lemmy.ml · 2 years agomessage-square152fedilink
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up31arrow-down3·2 years agoRust required you to fix all the errors before running the code.
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up15arrow-down1·2 years agoCompared to that trio, they are a rarity that make people excited just to spot one.
minus-squareTurun@feddit.delinkfedilinkarrow-up5·2 years agoI have a graphical application that crashes regularly when I switch between displays with Ctrl+alt+number. Something in the winit stack does not like it.
minus-squareasudox@lemmy.worldlinkfedilinkarrow-up2·edit-22 years agoRuntime errors are rare? Interesting. I guess it depends on how much error handling the dev additionally wants to do.
minus-squarecaseyweederman@lemmy.calinkfedilinkarrow-up8·2 years agoRust: this garbage code is beneath me, come back when you have your shit together.
minus-squareTurun@feddit.delinkfedilinkarrow-up2·2 years agoCompilation: top row, runtime: button row.
Where’s rust?
Rust required you to fix all the errors before running the code.
Runtime errors are still a thing.
Compared to that trio, they are a rarity that make people excited just to spot one.
I have a graphical application that crashes regularly when I switch between displays with Ctrl+alt+number. Something in the winit stack does not like it.
Runtime errors are rare? Interesting. I guess it depends on how much error handling the dev additionally wants to do.
Rust: this garbage code is beneath me, come back when you have your shit together.
Compilation: top row, runtime: button row.