Yeah, Rust already has major compile time issues.

TBH I thought it was for refactoring type safety. Making sure that the type is understood and not ready to just change wildly accidentally.

I do love rust. But I do like making fun of it too.

Although I don't see how rust is immature? Unless I missed the joke?

I really like C++ (I know, shoot me), and I think auto should be avoided at (almost) all costs.

One of the things I love about a language like C++ is that I can take one glance at the code and immediately know what types I'm working with. auto takes that away while adding almost no benefit outside of a little convenience while writing.

If I'm working with some very big template type that I don't want to write out, 99/100 times I'll just have a using somewhere to make it more concise. Hell, I'll have using vectord = std::vector<double> if I'm using a lot of them, because I think it makes the code more readable. Just don't throw auto at me.

Of course, the worst thing ever (which I've seen far too often) is the use of auto in examples in documentation. Fucking hell! I'm reading the docs because I don't know the library well! When you first bother to write examples, at least let me know the return type without needing to dig through your source code!

The problem is that lambdas with a capture aren’t strongly typed are uniquely typed, so you have to use decltype/auto. And if you pass such a lambda to a function you’ll have to use auto as well.

If you write a lambda with a capture that calls itself recursively you’ll have to pass it to itself as an auto argument as part of the call signature.

I think this article explains it better: https://artificial-mind.net/blog/2020/09/12/recursive-lambdas

Edit: fixed wrong terminology