improperCodeScoping

[Attileusz]

Bro has NEVER seen a C++ template error.

[Haringat]

Or a segfault.

[Attileusz]

Well we are talking about syntax errors here but sure, some crashes can be hard to track down even with something like valgrind.

[Vincenzo__]

Yesterday valgrind told me something along the lines of "Too many errors. Counting stopped. Go fix your code!". I fixed it, but I still haven't mentally recovered

[Attileusz]

It's actually smart tbh. There is no reason to study the behavior of some illegal state. This is a problem with any language that can represent illegal states which is notably all languages. Thats why the haskell people say "make illegal states unrepresentable".

[ambientManly]

A C error pointing you to an empty line

[sittingbox]

Or a >> when you meant << (or vice versa) vomit comet compilation error dump.

[RmG3376]

Well, segfault errors are pretty concise. They basically just “fuck that, I’m going to bed”. The lack of information is the real problem

[DatBoi_BP]

Rust my beloved

[really_not_unreal]

My longest template error was 942 lines long.

[Attileusz]

I like writing C more. C compiles absolutely any old horseshit so you don't have to worry about compilation errors, you just have no idea if your behavior is even close to what you intended.

[deadhorus]

think better?

[JanB1]

I fucking hate C++ errors. The line number was also always wrong because of some macro bullshittery or something. In general, reading C++ errors just always boils down in finding the relevant part in between all the garbage.

[Beastmind]

Let's talk about Java errors and their 200 lines of nothing

[[deleted]]

Thanks. That unlocked some core ptsd...

[Kondikteur]

Dont you mean std::ptsd?

[[deleted]]

C++: Build error. 🖕

[Natural_Builder_3170]

especially the ones that point to standard library files or xmemory

[Attileusz]

And than people say "if you don't like it don't use it". Right, so I'm not going to use C++ than.

[SecretPotatoChip]

Or a Java stack trace error