Nicholas Nethercote c5dadd0408 Use #[rustfmt::skip] on some use groups to prevent reordering. ... `use` declarations will be reformatted in #125443. Very rarely, there is a desire to force a group of `use` declarations together in a way that auto-formatting will break up. E.g. when you want a single comment to apply to a group. #126776 dealt with all of these in the codebase, ensuring that no comments intended for multiple `use` declarations would end up in the wrong place. But some people were unhappy with it. This commit uses `#[rustfmt::skip]` to create these custom `use` groups in an idiomatic way for a few of the cases changed in #126776. This works because rustfmt treats any `use` item annotated with `#[rustfmt::skip]` as a barrier and won't reorder other `use` items around it.		2024-07-19 13:26:48 +10:00
..
check_consts	Move trait selection error reporting to its own top-level module	2024-07-08 16:04:47 -04:00
const_eval	valtree construction: keep track of which type was valtree-incompatible	2024-07-18 11:58:16 +02:00
interpret	Use #[rustfmt::skip] on some use groups to prevent reordering.	2024-07-19 13:26:48 +10:00
util	rename CompileTimeInterpreter -> CompileTimeMachine, CompileTimeEvalContext -> CompileTimeInterpCx	2024-06-13 20:30:11 +02:00
errors.rs	don't ICE when encountering an extern type field during validation	2024-06-22 17:39:01 +02:00
lib.rs	use is_none_or in some places in the compiler	2024-06-12 16:20:07 +02:00