Will Crichton @tonofcrates@mastodon.social
Public

If you've ever struggled with trait/typeclass compiler errors, or if you're interested in better user interfaces for compiler diagnostics, check out our upcoming PLDI paper: "An Interactive Debugger for Rust Trait Errors"

Rust famously has good error messages. But we found that with the right interface, people become ~3x faster at identifying the root cause of a trait error. See our blog post, including a live demo in your browser:

cel.cs.brown.edu/blog/an-inter

A screenshot of the Argus tool for visualizing trait inference. It shows a VSCode panel with a Bevy program on the left containing a type error related to the `SystemParam` trait, and an Argus visualization of that error on the right.
0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/tonofcrates/statuses/114458524748209795 on your instance and quote it. (Note that quoting is not supported in Mastodon.)