Added in 12ac719, this logic always
passed --cpu-features, even when the value was the empty string.

replace build with check

Co-authored-by: Michael Goulet <michael@errs.io>

use appropriate test name

Migrate item_opaque_type to Askama

Fix wrap_item parameters

Fix to write

…laumeGomez

Migrate `item_opaque_ty` to Askama

This PR migrates `item_opaque_ty` to Askama

Refers: rust-lang#108868

…trochenkov

Avoid passing --cpu-features when empty

Added in 12ac719, this logic always
passed --cpu-features, even when the value was the empty string.

…rtlarsan68

bootstrap: remove dependency `is-terminal`

…lor-12, r=notriddle

Migrate GUI colors test to original CSS color format

Follow-up of rust-lang#111459.

r? `@notriddle`

…rrors

Add a test for rust-lang#105709

Closes rust-lang#105709

…errors

Fix ICE for while loop with assignment condition with LHS place expr

Fixes rust-lang#112385.

…henkov

Remove accidental comment

Left this in in rust-lang#110092 while debugging, thanks to `@WaffleLapkin` for spotting

…s, r=compiler-errors

Track more diagnostics in `rustc_expand`

I wish we could lint this somehow...

…=Nilstrieb

Don't `use compile_error as print`

I've spent **1.5 hours** debugging this while trying to compile rust-lang#112400, if we use `compile_error!`, we should not just forward user input to it, but issue a reasonable error message.

The better solution would be to use a lint like `clippy::print_stdout`, but since we don't have clippy in CI, let's at least make the macro error better.

Also note that some functions called here actually do use `println` (see for example `print_type_sizes` function).