devilish666@lemmy.world to Programmer Humor@lemmy.ml · 1 year agoC++ Momentlemmy.worldimagemessage-square153fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1imageC++ Momentlemmy.worlddevilish666@lemmy.world to Programmer Humor@lemmy.ml · 1 year agomessage-square153fedilink
minus-squarecaseyweederman@lemmy.calinkfedilinkarrow-up0·1 year agoRust: this garbage code is beneath me, come back when you have your shit together.
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up0·1 year agoRust required you to fix all the errors before running the code.
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up0·1 year agoCompared to that trio, they are a rarity that make people excited just to spot one.
minus-squareasudox@lemmy.worldlinkfedilinkarrow-up0·edit-21 year agoRuntime errors are rare? Interesting. I guess it depends on hoe much error handling the dev additionally wants to do.
minus-squareTurun@feddit.delinkfedilinkarrow-up0·1 year 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-squareTurun@feddit.delinkfedilinkarrow-up0·1 year agoCompilation: top row, runtime: button row.
Where’s rust?
Rust: this garbage code is beneath me, come back when you have your shit together.
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.
Runtime errors are rare? Interesting. I guess it depends on hoe much error handling the dev additionally wants to do.
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.
Compilation: top row, runtime: button row.