Struct cargo_culture_kit::HasRustfmtFile [−][src]
pub struct HasRustfmtFile;
Rule that asserts a good Rust project: "Should have a rustfmt.toml file in the project directory."
Justification
Code style linting is a valuable tool to enhance project-wide
consistency and readability for new developers.
rustfmt
is the de-facto standard style linter in the Rust
community.
A rustfmt.toml file suggests that the project
maintainers are aware of the advantages of unified formatting,
and have taken the time to select the rustfmt
rules that make
sense for this project, even if the choice is simply to use the
defaults.
Trait Implementations
impl Debug for HasRustfmtFile
[src]
impl Debug for HasRustfmtFile
fn fmt(&self, f: &mut Formatter) -> Result
[src]
fn fmt(&self, f: &mut Formatter) -> Result
Formats the value using the given formatter. Read more
impl Default for HasRustfmtFile
[src]
impl Default for HasRustfmtFile
fn default() -> HasRustfmtFile
[src]
fn default() -> HasRustfmtFile
Returns the "default value" for a type. Read more
impl Rule for HasRustfmtFile
[src]
impl Rule for HasRustfmtFile
fn description(&self) -> &'static str
[src]
fn description(&self) -> &'static str
The central tenet of this Rule
. Serves as a unique identifier for Rule instances, as well as a human-readable summary of what this Rule
means for a given project. Read more
fn evaluate(
&self,
cargo_manifest_file_path: &Path,
_verbose: bool,
metadata: &Option<Metadata>,
_print_output: &mut Write
) -> RuleOutcome
[src]
fn evaluate(
&self,
cargo_manifest_file_path: &Path,
_verbose: bool,
metadata: &Option<Metadata>,
_print_output: &mut Write
) -> RuleOutcome
Does the Rust project found at cargo_manifest_path
uphold this Rule
, as summarized in the description
? Read more
Auto Trait Implementations
impl Send for HasRustfmtFile
impl Send for HasRustfmtFile
impl Sync for HasRustfmtFile
impl Sync for HasRustfmtFile