# Poll: how much context to give for async error messages?

**URL:** <https://internals.rust-lang.org/t/poll-how-much-context-to-give-for-async-error-messages/11753>\
**Category:** compiler\
**Created:** [February 6, 2020, 4:30pm UTC](https://internals.rust-lang.org/t/poll-how-much-context-to-give-for-async-error-messages/11753 "2020-02-06T16:30:26Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![mcy](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/mcy/32/6512_2.png) [@mcy](https://internals.rust-lang.org/u/mcy)\
**Post date:** [February 6, 2020, 9:57pm UTC](https://internals.rust-lang.org/t/poll-how-much-context-to-give-for-async-error-messages/11753/14 "2020-02-06T21:57:12Z")

</div>

> [@nikomatsakis](#):
>
> If we were going to add a "verbose" flag, I was thinking that one of my main concerns would be people not knowing it's there, meaning that we do a lot of work to add it with little value

I do wonder if we could make `--explain` better... I like to imagine passing `--explain <u32 hash>` to `cargo check` would supress all errors except for one with that hash, and provide relevant expansion of it. This may be just a symptom of rustc not having something like the go compiler's "too many errors" error, though...

(Errors, of course, would have to include a note with the `--explain` hash...)

---

_[View the full topic](https://internals.rust-lang.org/t/poll-how-much-context-to-give-for-async-error-messages/11753)._
