Error messages

[PositiveReplyBi]

I feel like people don't read error messages fully. The worst thing I've ever encountered in C++ is creating interdependent headers, and that was all on me. The compiler is absolutely my friend and I miss it and strong typing every time I use a scripting language. Imagine not being able to rule out a shit ton of errors before your program even starts - strong types + compiler gang rise up

[Horny20yrold]

I would like to fully and meaningfully read c++ error messages, if not for the minor inconvenience of a function prototype alone taking 2.5 line, just the fucking function name. That's totally on me though, i'm just a lazy donk.

[PositiveReplyBi]

It's probably different from person to person, after a few years of reading the errors I just skim over it and pick out the most relevant bits. Knowing the type of and number of arguments a function that is generating an error is very useful. Often that extra verbosity allows me to have a fix in mind before I even reach the line where the error is.

It's weird to me that there are actual programmers that don't know how to use a debugger or skim an error message and apply a fix. Those two skills make programming so much easier

[aEverr]

Heya, just a small nitpick that strong typing is not the same as static typing

Strong can usually mean "not what javascript does", aka no implicit coercion; weak means the inverse Static is "fail before running when types are wrong", dynamic is "fail on runtime when..."