0x0@lemmy.zip to Programmer Humor@programming.dev · 13 days agorace conditionslemmy.zipimagemessage-square87fedilinkarrow-up1882arrow-down125
arrow-up1857arrow-down1imagerace conditionslemmy.zip0x0@lemmy.zip to Programmer Humor@programming.dev · 13 days agomessage-square87fedilink
minus-squareILikeBoobies@lemmy.calinkfedilinkarrow-up42·13 days agoWhy is the crab not Rust. This is outrageous, it’s unfair
minus-squared_k_bo@feddit.orglinkfedilinkarrow-up37arrow-down1·edit-213 days agoRust would be some borrow checker compile error like borrowed data escapes outside of associated function argument requires that `'1` must outlive `'static`
minus-squarepewgar_seemsimandroid@lemmy.blahaj.zonelinkfedilinkarrow-up17·12 days agorust errors are funny if you don’t know rust
minus-squaremilicent_bystandr@lemm.eelinkfedilinkarrow-up13·12 days ago News at Ten: Borrowed Data Escapes Outside of Associated Function
minus-squareEphera@lemmy.mllinkfedilinkEnglisharrow-up8·12 days agoThose also happen to be errors you’d typically run into, if you don’t yet really know Rust…
minus-squared_k_bo@feddit.orglinkfedilinkarrow-up2·edit-212 days agoI do run into them even though I use Rust for ~3 years now, but only in non-obvious cases, e. g. when all references to the borrowed data are dropped before the end of the function.
minus-squarejumping_redditor@sh.itjust.workslinkfedilinkarrow-up0·13 days agoyou can still segfault in rust iirc
minus-squarejenesaisquoi@feddit.orglinkfedilinkEnglisharrow-up1·12 days agoNot in safe Rust. Only if you explicitly tell the compiler “I got this, don’t worry” but then fuck up.
minus-squarejumping_redditor@sh.itjust.workslinkfedilinkarrow-up0·12 days agohttps://github.com/Speykious/cve-rs
minus-squarejumping_redditor@sh.itjust.workslinkfedilinkarrow-up0·12 days agoI guess they fixed the weirdness involving calling main later in the program
minus-squareEphera@lemmy.mllinkfedilinkEnglisharrow-up1·11 days agoAs in, you call main() recursively? Don’t think, I’ve ever tried that in any language…
Why is the crab not Rust. This is outrageous, it’s unfair
Rust would be some borrow checker compile error like
borrowed data escapes outside of associated functionargument requires that `'1` must outlive `'static`rust errors are funny if you don’t know rust
Those also happen to be errors you’d typically run into, if you don’t yet really know Rust…
I do run into them even though I use Rust for ~3 years now, but only in non-obvious cases, e. g. when all references to the borrowed data are dropped before the end of the function.
you can still segfault in rust iirc
Not in safe Rust. Only if you explicitly tell the compiler “I got this, don’t worry” but then fuck up.
https://github.com/Speykious/cve-rs
I guess they fixed the weirdness involving calling main later in the program
As in, you call
main()recursively? Don’t think, I’ve ever tried that in any language…