An Interactive Debugger for Rust Trait Errors

Maybe the example is contrived in a way that does not show the issue very clearly.<p>User forgot to include the posts table in the query.<p>Error line 1 says &quot;Cannot select `posts::columns::id` from `users::table`.<p>For me, that is more than enough to spot the issue. But if I had missed my morning coffee, 5 lines below I have extra help: &quot;note: `posts::columns::id` is no valid selection for `users::table`&quot;<p>The rest of the &quot;help&quot; lines I can happily ignore.

Would have been very useful during my Scala days, I often had lots of type errors with long stacks (heard Scala is different today) that took quite some time to fix.<p>Some years ago I came to the conclusion I like Rust compiler errors the most<p><a href="https:&#x2F;&#x2F;www.inkmi.com&#x2F;blog&#x2F;developer-productivity-compiler-errors" rel="nofollow">https:&#x2F;&#x2F;www.inkmi.com&#x2F;blog&#x2F;developer-productivity-compiler-e...</a>

Feels like Zig&#x27;s comptime call stacks would make for better error reports than these Rust Traits.

LOL. People raked C++ over the coals for having metaprogramming sophisticated enough to need debugging. People mocked projects like Templight (<a href="https:&#x2F;&#x2F;llvm.org&#x2F;devmtg&#x2F;2015-04&#x2F;slides&#x2F;EuroLLVM2015Templight.pdf" rel="nofollow">https:&#x2F;&#x2F;llvm.org&#x2F;devmtg&#x2F;2015-04&#x2F;slides&#x2F;EuroLLVM2015Templight...</a>) as just providing how awful C++ is. Now, when the same thing appears for Rust, it&#x27;s evidence of how awesome Rust is?

&quot;rust traitors&quot;