Implementing and adopting probes where possible (MMU, etc.) was absolutely the right path to go down.
Fair enough; failing data a risk guestimate will have to be used to prioritize.
-
-
But prio minor perf gain over sec.risk when "safe" is 1st keyword in project goal? Odd
-
I did not personally make this call.
-
Not accusing anyone, just explaining my point of view on such matters.
-
no worries, i totally hear you.
End of conversation
New conversation -
-
-
It's a red herring anyway since the choice they made was to add a soundness hole.
-
If they had done NOTHING, this would not be a memory safety hole. 1-2% lost perf.
-
Sure, a feature that LLVM doesn't have could be used to implement cheaper safety.
-
Someone actually implemented it and it was rejected for inclusion in Rust's LLVM.
-
They could have used it when available, otherwise fall back to the existing checks.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.