Aaron Hill 168e35d569 Include a span in more expected...found notes ... In most places, we use a span when emitting `expected...found` errors. However, there were a couple of places where we didn't use any span, resulting in hard-to-interpret error messages. This commit attaches the relevant span to these notes, and additionally switches over to using `note_expected_found` instead of manually formatting the message		2019-12-03 23:13:10 -05:00
..
assoc-type.rs	Remove licenses	2018-12-25 21:08:33 -07:00
assoc-type.stderr	Remove licenses	2018-12-25 21:08:33 -07:00
dyn-trait.nll.stderr	update tests	2019-10-27 09:39:14 -05:00
dyn-trait.rs	Remove licenses	2018-12-25 21:08:33 -07:00
dyn-trait.stderr	Include a span in more expected...found notes	2019-12-03 23:13:10 -05:00
explicit-and-elided-same-header.rs	Remove licenses	2018-12-25 21:08:33 -07:00
inherent-impl.rs	Migrate compile-pass annotations to build-pass	2019-07-03 06:30:28 +09:00
path-elided.rs	Disallow non-explicit elided lifetimes in async fn	2019-05-01 18:34:49 -07:00
path-elided.stderr	Disallow non-explicit elided lifetimes in async fn	2019-05-01 18:34:49 -07:00
path-underscore.rs	Remove licenses	2018-12-25 21:08:33 -07:00
ref-underscore.rs	Remove licenses	2018-12-25 21:08:33 -07:00
trait-elided.rs	Disallow non-explicit elided lifetimes in async fn	2019-05-01 18:34:49 -07:00
trait-elided.stderr	Disallow non-explicit elided lifetimes in async fn	2019-05-01 18:34:49 -07:00
trait-underscore.rs	Remove licenses	2018-12-25 21:08:33 -07:00