11 Commits

Author	SHA1	Message	Date
Aaron Hill	23018a55d9	Implement rustc side of report-future-incompat	2020-10-30 20:02:14 -04:00
est31	215cd36e1c	Remove unused code from remaining compiler crates	2020-10-14 04:14:32 +02:00
marmeladema	bb8e1764bb	Simplify some match statements on `DefPathDataName'	2020-09-25 22:46:15 +01:00
marmeladema	657ecdb75e	Rename DefPathData::get_name() to DefPathData::name()	2020-09-25 22:46:15 +01:00
marmeladema	f1878d19fa	Move from {{closure}}#0 syntax to {closure#0} for (def) path components	2020-09-25 22:46:14 +01:00
Bastian Kauschke	bfa2030ccb	update docs	2020-09-19 15:36:53 +02:00
Bastian Kauschke	0eecbd4f97	wording	2020-09-19 11:33:11 +02:00
Bastian Kauschke	4debbdc6b9	transmute: use diagnostic item	2020-09-19 11:33:11 +02:00
LeSeulArtichaut	3e14b684dd	Change ty.kind to a method	2020-09-04 17:47:51 +02:00
Dan Aloni	07e7823c01	pretty: trim paths of unique symbols ... If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.	2020-09-02 22:26:37 +03:00
mark	9e5f7d5631	mv compiler to compiler/	2020-08-30 18:45:07 +03:00