devilish666@lemmy.world to Programmer Humor@lemmy.ml · 9 months agoC++ Momentlemmy.worldimagemessage-square156fedilinkarrow-up11.03Karrow-down132
arrow-up1999arrow-down1imageC++ Momentlemmy.worlddevilish666@lemmy.world to Programmer Humor@lemmy.ml · 9 months agomessage-square156fedilink
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up31arrow-down3·9 months agoRust required you to fix all the errors before running the code.
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up15arrow-down1·9 months agoCompared to that trio, they are a rarity that make people excited just to spot one.
minus-squareTurun@feddit.delinkfedilinkarrow-up5·9 months 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-29 months 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·9 months agoRust: this garbage code is beneath me, come back when you have your shit together.
minus-squareTurun@feddit.delinkfedilinkarrow-up2·9 months 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.