I'm not a rust user myself, but I'm guessing from all the references to raw pointers that a lot of the code referenced here is actually not idiomatic for all but small snippets of high perf code, so maybe the complexity is not going to affect too many people.
I think this approach shows a high level of disrespect for users.
Compiler afaik will never be able to correctly 100% identify you are or aren't breaking some properties due to Rice's Theorem.
That said, you're committing a Nirvana fallacy. Perfect doesn't prevent improvement.
E.g. seatbelts don't prevent being stabbed by a large metal pole, ergo it's useless.
Every week I see newbies coming and asking why won't compiler allow this - and then point a hugely unsafe action.
Hell, I ran into a similar issue. I wanted to expose something mutable as immutable. My argumentation was but it was immutable at time of calling. However as someone in Rust discord pointed, using that you could cause UB trivially.
Nobody here is talking about 100%. I responded to a post that has left me with the impression that it is up to the user to bend backwards and make their brains work as a compiler rather than try to improve compiler.
What do you mean? You always have to track lifetimes and what outlives what (i.e. work of a compiler). Especially in C++. Not doing that results in UB.
In Rust you have a compiler double checking you. And it errs on side of caution. And no, errors aren't horrible, they come with suggestions for fixing them.
Lifetimes don't go away just because there isn't a borrow checker or way to define them in the source code.
Compiler being obtuse and not being able to figure when it is safe to "break rules" is the problem. Not twisting brain of the programmer into being "safe compiler". This sounds like a Stockholm syndrome.
>"you should be following immutable practices"
No I should not. I should do what makes sense in particular situation and not bending over for some zealots trying to enforce one and the only way.