Great read. Did @rustlang people know about @swiftlang's overflow checking optimizations? A topic worth revisiting.https://twitter.com/johnregehr/status/718199181295362049 …
@BRIAN_____ @CopperheadSec @rustlang I doubt we would ignore significant optimizations because we have an unwinding mode.
-
-
@wycats@CopperheadSec@rustlang Good to hear. Looking forward to seeing the improvements. -
@BRIAN_____@wycats@CopperheadSec it just so happens that https://twitter.com/rustlang/status/718545850226589696 … just happened! -
@rustlang@wycats@CopperheadSec Good to hear. If I understand the RFC correctly, though, it requires substituting a custom libstd? -
@BRIAN_____@rustlang getting full benefit requires a std with special flags, but work on better cross-compilation makes this easy. -
@huon_w@BRIAN_____@rustlang in other words, we make progress incrementally :) slow and steady wins the race.
End of conversation
New conversation -
-
-
@wycats@BRIAN_____@rustlang There's already lots of code in the standard libraries with major design compromises due to unwinding. -
@wycats@BRIAN_____@rustlang Such as using swaps instead of one-way copies. There has never been interest in first-class nounwind support. -
@CopperheadSec@BRIAN_____@rustlang I can only speak for myself but I'm interested. I believe others are interested as well. -
@CopperheadSec@BRIAN_____@rustlang again, I can only speak for myself, but first-class nounwind is a personal priority. -
@CopperheadSec@BRIAN_____@rustlang at minimum, it will stop rust libs from cargo culting the go recover-in-libs antipattern.
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.