Hal-5700X@sh.itjust.works to Technology@lemmy.worldEnglish · 4 个月前Microsoft wants to replace its entire C and C++ codebase, perhaps by 2030www.theregister.comexternal-linkmessage-square129linkfedilinkarrow-up1259arrow-down114cross-posted to: [email protected]
arrow-up1245arrow-down1external-linkMicrosoft wants to replace its entire C and C++ codebase, perhaps by 2030www.theregister.comHal-5700X@sh.itjust.works to Technology@lemmy.worldEnglish · 4 个月前message-square129linkfedilinkcross-posted to: [email protected]
minus-squareⓂ3️⃣3️⃣ 🌌@lemmy.ziplinkfedilinkEnglisharrow-up5arrow-down5·4 个月前That’s funny because using unsafe might be an hint that Rust is not the right tool for the job. Yet we have rust in the kernel, rust coreutils… I just can’t wrap my head arout it, yet.
minus-squareboaratio@lemmy.worldlinkfedilinkEnglisharrow-up3arrow-down1·4 个月前You shouldn’t have said that. Now the rust zealots are going to come for you.
minus-squareⓂ3️⃣3️⃣ 🌌@lemmy.ziplinkfedilinkEnglisharrow-up2arrow-down1·4 个月前Got downvoted, here they come…
minus-squarefilcuk@lemmy.ziplinkfedilinkEnglisharrow-up1·4 个月前Unsafe is expected and necessary in certain situations. Using other languages doesn’t change that fact. It’s talked about in the docs
That’s funny because using unsafe might be an hint that Rust is not the right tool for the job. Yet we have rust in the kernel, rust coreutils… I just can’t wrap my head arout it, yet.
You shouldn’t have said that. Now the rust zealots are going to come for you.
Got downvoted, here they come…
Unsafe is expected and necessary in certain situations. Using other languages doesn’t change that fact.
It’s talked about in the docs