hckrnws

Maybe the example is contrived in a way that does not show the issue very clearly.

User forgot to include the posts table in the query.

Error line 1 says "Cannot select `posts::columns::id` from `users::table`.

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: "note: `posts::columns::id` is no valid selection for `users::table`"

The rest of the "help" 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.

Some years ago I came to the conclusion I like Rust compiler errors the most

https://www.inkmi.com/blog/developer-productivity-compiler-e...

Feels like Zig's comptime call stacks would make for better error reports than these Rust Traits.

Honestly, I think the mismatch is that you have a code that tries too much to do with Traits.

A simpler, more jooq like interface with strings would work about just as well.

Type issues no longer a problem when you throw out the type system entirely!

"rust traitors"

Came to see if someone’s brain parsed it that way too!