rust/tests/ui/error-emitter/highlighting.rs

// Make sure "highlighted" code is colored purple

//@ compile-flags: --error-format=human --color=always
//@ error-pattern:[35mfor<'a> [0m
//@ edition:2018
// Temporary until next release:
//@ ignore-stage2

use core::pin::Pin;
use core::future::Future;
use core::any::Any;

fn query(_: fn(Box<(dyn Any + Send + '_)>) -> Pin<Box<(
    dyn Future<Output = Result<Box<(dyn Any + 'static)>, String>> + Send + 'static
)>>) {}

fn wrapped_fn<'a>(_: Box<(dyn Any + Send)>) -> Pin<Box<(
    dyn Future<Output = Result<Box<(dyn Any + 'static)>, String>> + Send + 'static
)>> {
    Box::pin(async { Err("nope".into()) })
}

fn main() {
    query(wrapped_fn);
}
-												use magenta instead of bold for highlighting

according to a poll of gay people in my phone, purple is the most popular color to use for highlighting

| color      | percentage |
| ---------- | ---------- |
| bold white | 6%         |
| blue       | 14%        |
| cyan       | 26%        |
| purple     | 37%        |
| magenta    | 17%        |

unfortunately, purple is not supported by 16-color terminals, which rustc apparently wants to support for some reason.
until we require support for full 256-color terms (e.g. by doing the same feature detection as we currently do for urls), we can't use it.

instead, i have collapsed the purple votes into magenta on the theory that they're close, and also because magenta is pretty.

											
										
										
											2023-12-08 13:09:10 -06:00
+								// Make sure "highlighted" code is colored purple
 								//@ compile-flags: --error-format=human --color=always
 								//@ error-pattern:[35mfor<'a> [0m
 								//@ edition:2018
-												On tests that specify --color=always emit SVG file with stderr output

Leverage `anstyle-svg`, as `cargo` does now, to emit `.svg` files
instead of `.stderr` files for tests that explicitly enable color
output. This will make reviewing changes to the graphical output of
tests much more human friendly.

											
										
										
											2024-03-02 16:36:52 -06:00
+								// Temporary until next release:
 								//@ ignore-stage2
-												use different revisions for testing colors on windows

this is kinda jank because it means people need both machines to bless the tests

											
										
										
											2023-12-09 07:40:55 -06:00
-												use magenta instead of bold for highlighting

according to a poll of gay people in my phone, purple is the most popular color to use for highlighting

| color      | percentage |
| ---------- | ---------- |
| bold white | 6%         |
| blue       | 14%        |
| cyan       | 26%        |
| purple     | 37%        |
| magenta    | 17%        |

unfortunately, purple is not supported by 16-color terminals, which rustc apparently wants to support for some reason.
until we require support for full 256-color terms (e.g. by doing the same feature detection as we currently do for urls), we can't use it.

instead, i have collapsed the purple votes into magenta on the theory that they're close, and also because magenta is pretty.

											
										
										
											2023-12-08 13:09:10 -06:00
+								use core::pin::Pin;
 								use core::future::Future;
 								use core::any::Any;
 								fn query(_: fn(Box<(dyn Any + Send + '_)>) -> Pin<Box<(
 								    dyn Future<Output = Result<Box<(dyn Any + 'static)>, String>> + Send + 'static
 								)>>) {}
 								fn wrapped_fn<'a>(_: Box<(dyn Any + Send)>) -> Pin<Box<(
 								    dyn Future<Output = Result<Box<(dyn Any + 'static)>, String>> + Send + 'static
 								)>> {
 								    Box::pin(async { Err("nope".into()) })
 								}
 								fn main() {
 								    query(wrapped_fn);
 								}