Struct bootstrap::core::build_steps::test::Tidy

pub struct Tidy;

Trait Implementations

impl Clone for Tidy

fn clone(&self) -> Tidy

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Tidy

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Hash for Tidy

fn hash<__H: Hasher>(&self, state: &mut __H)

Feeds this value into the given Hasher.

fn hash_slice<H>(data: &[Self], state: &mut H)

where H: Hasher, Self: Sized,

Feeds a slice of this type into the given Hasher.

impl PartialEq for Tidy

fn eq(&self, other: &Tidy) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Step for Tidy

fn run(self, builder: &Builder<'_>)

Runs the tidy tool.

This tool in src/tools checks up on various bits and pieces of style and otherwise just implements a few lint-like checks that are specific to the compiler itself.

Once tidy passes, this step also runs fmt --check if tests are being run for the dev or nightly channels.

type Output = ()

PathBuf when directories are created or to return a Compiler once it’s been assembled.

const DEFAULT: bool = true

Whether this step is run by default as part of its respective phase. true here can still be overwritten by should_run calling default_condition.

const ONLY_HOSTS: bool = true

If true, then this rule should be skipped if –target was specified, but –host was not

fn should_run(run: ShouldRun<'_>) -> ShouldRun<'_>

When bootstrap is passed a set of paths, this controls whether this rule will execute. However, it does not get called in a “default” context when we are not passed any paths; in that case, make_run is called directly.

fn make_run(run: RunConfig<'_>)

Builds up a “root” rule, either as a default rule or from a path passed to us.

impl Eq for Tidy

impl StructuralPartialEq for Tidy

Layout

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.

Size: 0 bytes