I think Rust needs to show me a decision tree for why something on the lefthand side of a function call ends up being whatever vscode + lsp shows me. Because th

I think Rust needs to show me a decision tree for why something on the lefthand side of a function call ends up being whatever vscode + lsp shows me. Because the compiler and rust-analyzer are going through various traits and auto-traits to ultimately land on one decision but if I want to understand how Rust works I need to know how it arrives at these conclusions. I don't want to have to jump deep down into language constructs and read the docs just to find out several levels deep that a trait was implemented by some other trait that then had an auto trait impl and that's why it ends up requiring me to write &. Rust being complex is fine but only if they go far beyond what has been standard tooling.