Aaron Hill dea8a16af5 Avoid describing a method as 'not found' when bounds are unsatisfied ... Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note.		2021-01-26 23:59:50 -05:00
..
json	mv compiler to compiler/	2020-08-30 18:45:07 +03:00
annotate_snippet_emitter_writer.rs	Implement rustc side of report-future-incompat	2020-10-30 20:02:14 -04:00
diagnostic.rs	Switch compiler/ to intra-doc links	2020-12-18 15:22:51 -05:00
diagnostic_builder.rs	Avoid describing a method as 'not found' when bounds are unsatisfied	2021-01-26 23:59:50 -05:00
emitter.rs	Replace tabs earlier in diagnostics	2020-12-09 10:12:15 +00:00
json.rs	Some work	2020-10-30 20:02:14 -04:00
lib.rs	Use Option::map_or instead of .map(..).unwrap_or(..)	2021-01-14 19:23:59 +01:00
lock.rs	mv compiler to compiler/	2020-08-30 18:45:07 +03:00
registry.rs	mv compiler to compiler/	2020-08-30 18:45:07 +03:00
snippet.rs	Fix even more clippy warnings	2020-10-30 10:13:39 -04:00
styled_buffer.rs	Replace tabs earlier in diagnostics	2020-12-09 10:12:15 +00:00