let’s not act like Java’s error log is useful
skill issue
The same applies to using the core dump.
In fact, the Python one is the lest useful of the trio.
It’s extraordinarily useful
Nevermind that the C++ program is two orders of magnitude faster when completed.
I would love to learn and use Rust but I’m a embedded systems guy. Everything of consequence is C and C++.
Rust seems pretty performant
https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/rust-gpp.html
I meant faster than Python, not faster than Rust. Rust is fast.
If the embedded system is old or poorly-maintained enough, there might be more Rust than you’d think.
There’s embedded rust for a few platforms. Using it on ESPs is fun
My favorite compile error happened while I was taking a Haskell class.
ghc: panic! (the ‘impossible’ happened)
The issue is plainly stated, and it provides clear next steps to the developer.
I had a similar error, though not from the compiler
Error message just readthis should never happen
This C++ message has an urgency vibes to it:
“Segmentation fault!! Drop the Nuclear Reactor quick!!”
At least you are getting a dump, count your blessings. Could be worse!
Just hook your app to a debugger and load the dump.
More like 100 lines of template errors
If only I could show segfaul stack tracetrough looped macros.
It breaks VSCode (it would be hilarious if I wasn’t the author of said macros).
No bounds checking, only fast.
Python: So you used spaces and tabs for indentation? NOW DIE!
Are you ok?
Mixing spaces and tabs should be a warcrime.
And in Python, it’s merely a SyntaxCrime.
Joke on you until the python program segfaults
The developer must either provide the logging and attach a debugger or go get fucked when a runtime error happens
are you c++?
That’s not true though. You can get the backtrace and other useful information from the coredump mentioned by the error message by loading it with gdb. Not as good as attaching it to a living process, since you can’t see step-by-step what happens leading up to the error, but still quite useful.
Well yes, that’s a pretty good way of debugging a third party app but if you are developing something you can have more ease with gdb attached
Where’s rust?
Rust required you to fix all the errors before running the code.
Runtime errors are still a thing.
Compared to that trio, they are a rarity that make people excited just to spot one.
Runtime errors are rare? Interesting. I guess it depends on hoe much error handling the dev additionally wants to do.
Why doesn’t JavaScript have tracebacks?
How useful would they be when they rely to such a large extent on various callback functions?
Except the C++ “Core dumped” line is telling you it just wrote a file out with the full state of the program at the time of the crash, you can load it up and see where it crashed and then go and look at what every local variable was at the time of the crash.
Pretty sure you can even step backwards in time with a good debugger to find out exactly how you got to the state you’re currently in.
C#: Time for a treasure hunt! Find the Null Reference Exception. Here’s a map. X marks the spot.
C# tells you the call site/method name and line number right at the top. It’s only really annoying when you have aggregate exceptions, which sometimes occur because someone async’d wrong
Actually getting there is the other part. It’s not like java where you can go down the chain if the problem isn’t where it says it is.
Rust developer: I’d like to compile some code
Rust compiler: the fuck you are
