It’s ok, you run the expression debugger, which says the first step, which is all of the formula, will result in an error. So helpful.

The world's angriest compiler.

So that's what inspired Vigil...

Tbf, you have to be pretty far with Rust to get to a point where Rust's compiler errors stop helping you (at least, as far as I've seen). After that, it's pretty much the same

yeah as nice as it is what you can achieve with trait-bounds there are definitely trade-offs, being compile time and error messages, and sometimes mental complexity, understanding what the trait-bounds exactly mean... I really hope, that this area gets improvement on at least the error-messages and compile time (incremental cached type-checking via something like salsa)

What about the fact it invades your dreams and slowly drives you insane?

Why is it written in Vietnamese though?

Syntax error: unmatched thing in thing from std::nonstd::__map<_Cyrillic, _$$$dollars>const basic_string< epic_mystery,mongoose_traits, __default_alloc_>

(from James Mickens' The Night Watch, highly recommended with his other essays: https://mickens.seas.harvard.edu/wisdom-james-mickens)

Template>, Outer>>>::static_wrapper, spirit::parser::lever>::fuck_you

The good thing about Rust is that if you have no idea of any problem in your code, it very likely because your code is ok.

On C++ things are different.

Oracle: You have this error in line 1

User: Hey, no, there isn't anything to cause this error in line 1

Oracle: I'm telling you, it's in line 1

User: Hum... How many lines are in my 10 lines query?

Oracle: 1

Have you tried segmenting in a non-faulty way?

Probably forgot a semicolon

The range those words induce is crazy

Rust because having a package manager is important.

Even C has a package manager

Bebop, he would just submit his code to the Shredder.