Removing the existing solution and leaving a gaping undocumented memory safety hole was irresponsible.
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 -
-
-
They could have had the performance gain by accepting stack probe PR to Rust LLVM.
-
And just setting it up to use it when available, otherwise use existing mechanism.
End of conversation
New conversation -
-
-
approach overall to the problem
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
and again, in my understanding, not about the perf gain. but that it's the right
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.