On the contrary, the borrow checker is basically the first thing you learn about when writing in Rust as it’s the primary “gimmick” of the language. Anyone writing a non-trivial program should have at least heard the term before, even if they don’t fully understand how it works.

The borrow checker is a feature of Rust’s compiler which places strict constraints on ownership of data to guarantee memory safety. It adds a lot of friction to writing Rust code if you’re not experienced with the language (or sometimes even if you are). OP refers to the “language restriction of Rust”, seemingly talking about the borrow checker, but has never even heard of it. It’s kind of like someone claiming they didn’t vibecoded their C++ project but having no idea what the STL is.

That was obviously a joke though, and it wasn’t even OP.

I don’t disagree that the language is a great way to build an understanding of object lifecycles, but in my experience C++ ctors and dtors are also the biggest source of confusing footguns I’ve ever encountered in any programming language.

Separately, template metaprogramming is a whole different beast. It’s an extremely powerful tool, but to me it also feels like finding the correct incantation to get it to do exactly what you need for more complex scenarios. It can be really fun if you know what you’re doing, but it also tends to make me very upset at the compiler when my incantations are a bit off.

Yeah, it’s not grammatically correct AFAIK but it’s a fairly common mistake to see.