Could I get feedback on this #rust compiler error? Even if (or maybe particularly if!) you're not familiar with #rustlang, can you understand what's happening? Are there things you'd change of this output?
I think I've gotten to the best possible output for this #rust error that I can manage today, removing as much unnecessary context and being as localized as I can. And we got a bonus structured suggestion too!
"We spent decades trying to invent a sufficiently smart compiler when we should have been inventing a sufficiently empathetic one."Rust Compiler team member. If you have to search for answers when the compiler is talking to you, that's a bug.There are no bad programmers, only insufficiently advanced compilers.Cache-locality awareness evangelist.💼@aws, opinions my ownhe/himTrans rights are human rights