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
..
comments	Add test for block doc comments horizontal trim	2022-02-07 17:07:53 +01:00
case.rs	Replace some bool params with an enum	2022-10-01 10:13:02 +00:00
classify.rs	Move let expression checking to parsing	2023-09-11 15:51:18 +00:00
comments.rs	more clippy::style fixes:	2023-07-23 23:39:04 +02:00
literal.rs	Use Option::is_some_and and Result::is_ok_and in the compiler	2023-05-24 14:20:41 +00:00
parser.rs	Improve spans for indexing expressions	2023-08-04 13:17:39 +02:00
unicode.rs	Remove dependency on slice_internals feature in rustc_ast	2023-01-22 13:05:47 +01:00