Stack traces, human panic, and failure::Context are essentially runtime docs. They provide contextual information when something goes wrong. Output depends on what went wrong. Also you'll never want them ahead of time, but only when inspecting the program.
-
Show this thread
-
I guess the compiler error messages are quite similar. Super contextual, and completely dependent on the input state you gave it. Imagine if we could make a similar leap the compiler has for compilation errors, but for in-program runtime error reporting. We should experiment :D
1 reply 2 retweets 13 likesShow this thread -
(oh oh oh, just like, imagine if debug Rust could point to the line in source that the program broke, and explain how it broke, and why. Would be so much better than staring at a 50 line stack trace)
3 replies 0 retweets 9 likesShow this thread
Oh wait, I forgot about miri. Very excited again about what miri will make possible. Wonder if we could extend that workflow. Both for debug and release Rust, though probably to different degrees.
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.