Matthew Jasper 333388fd3c Move let expression checking to parsing ... There was an incomplete version of the check in parsing and a second version in AST validation. This meant that some, but not all, invalid uses were allowed inside macros/disabled cfgs. It also means that later passes have a hard time knowing when the let expression is in a valid location, sometimes causing ICEs. - Add a field to ExprKind::Let in AST/HIR to mark whether it's in a valid location. - Suppress later errors and MIR construction for invalid let expressions.		2023-09-11 15:51:18 +00:00
..
attr_wrapper.rs	Adjust to_attr_token_stream.	2023-09-06 17:12:07 +10:00
attr.rs	Avoid too many expected symbols and reduce Nones	2023-08-03 08:56:31 +00:00
diagnostics.rs	inlined kind	2023-08-08 10:59:15 +08:00
expr.rs	Move let expression checking to parsing	2023-09-11 15:51:18 +00:00
generics.rs	fix couple of clippy findings:	2023-07-23 10:50:14 +02:00
item.rs	Add explanatory note to 'expected item' error	2023-09-06 09:05:07 +05:30
mod.rs	Move let expression checking to parsing	2023-09-11 15:51:18 +00:00
nonterminal.rs	Rename NtOrTt as ParseNtResult.	2023-08-18 16:50:41 +10:00
pat.rs	Rollup merge of #113999 - Centri3:macro-arm-expand, r=wesleywiser	2023-08-04 07:25:45 +02:00
path.rs	Avoid too many expected symbols and reduce Nones	2023-08-03 08:56:31 +00:00
stmt.rs	Avoid too many expected symbols and reduce Nones	2023-08-03 08:56:31 +00:00
ty.rs	suggest removing impl in generic trait bound position	2023-08-29 20:27:38 +02:00