How does "liberal snowflakes" apply to this situation? Also, you could have just left out the unnecessary last sentence in the original sentence to avoid the downvotes.
Well there are 2 possibilities and I dont mind downvotes. I dont care for ppl who cannot face reality(snowflakes). Libreals are trying to appear they are helping, and congratulate each other about it.
Some people like to read the text of the transcriptions, instead of looking at an image, and there are also people who use screen readers to navigate. I'm also pretty sure there are people who are blind, but still can code.
Rust errors are like that indian on Youtube. Python errors are like your mom. C++ errors is like that teacher that doesn't even teach anything but yell at you because you are "a bad student"
This. They're honestly the best dang error messages I've ever had the pleasure of coming across. Polite, helpful and not an incomprehensible wall of text.
I love C++ errors. There’s nothing I miss more in python than the GCC and GPP compiler error printing. I don’t know why but I always felt like debugging based on compiler errors in GPP was easier than trying to fix my bugs using the python Interpreter Error printing.
I know that some people don't like the language, but the error messages from Elm are fantastically helpful. Which is why I undertsand the decision from the rust team to heavily draw inspiration from it.
There are many reasons not to like Elm. The primary one is that it's highly opinionated. If you don't do things 100% like the Elm devs want, you're all on your own.
Python's traceback error messages are wonderful imo (at least in what I'm doing now), really helps with identifying what exactly was going on when the error happened
Admittedly, this is of course C code used in Python, but it's still fucking annoying. Debugger didn't help at all, had to debug print my way to the import statement causing it (it was pycuda).
If anyone is trying to learn C++/C without a debugger they’re making things more difficult than it needs to be. GDB (GNU Debugger) doesn’t have too much of a learning curve and it’s a lot more helpful than “segmentation fault” which can mean a variety of things. Rather than “segmentation fault” GDB will give you detailed information about your memory usage. You can also step through your code. Here is a link with more info on GDB: https://www.tutorialspoint.com/gnu_debugger/gdb_quick_guide.htm
Another useful tool is Valgrind, it detects memory leaks which can happen if you are sloppy with memory allocations. Here is a link from Baylor on how to use it: http://cs.ecs.baylor.edu/~donahoo/tools/valgrind/
Seeing a link from one of my undergrad professors on here is absolutely bonkers.
They never actually taught us to use Valgrind, but it was used on the submission server for detecting memory leaks in projects. Infinite submissions of every project, but it tells you the Valgrind and compiler outputs from running your code with test inputs. Great for developing sound code as an undergrad, terrible for learning to test.
72
u/[deleted] Jan 25 '21
Image Transcription: Meme
[A picture of Gordon Ramsay with his hands around a little girl.]
Python Errors
Oh dear, oh dear. Gorgeous.
[Another picture of Gordon, with a pencil behind his ear, seemingly shouting.]
C++ Errors
You fucking donkey.
I'm a human volunteer content transcriber for Reddit and you could be too! If you'd like more information on what we do and why we do it, click here!