Struct IOError 

pub struct IOError {
    pub message: String,
}

What it does

This is not a regular diagnostic; instead, it’s raised when a file cannot be read from disk.

Why is this bad?

An IOError indicates an error in the development setup. For example, the user may not have permissions to read a given file, or the filesystem may contain a broken symlink.

Example

On Linux or macOS:

$ echo 'print("hello world!")' > a.py
$ chmod 000 a.py
$ ruff a.py
a.py:1:1: E902 Permission denied (os error 13)
Found 1 error.

References

• UNIX Permissions introduction
• Command Line Basics: Symbolic Links

Fields

message: String

Trait Implementations

impl Violation for IOError

E902

fn message(&self) -> String

The message used to describe the violation.

fn message_formats() -> &'static [&'static str]

Returns the format strings used by message.

const FIX_AVAILABILITY: FixAvailability = FixAvailability::None

None in the case a fix is never available or otherwise Some FixAvailability describing the available fix.

fn fix_title(&self) -> Option<String>

Returns the title for the fix. The message is also shown as an advice as part of the diagnostics.

fn into_diagnostic(self, range: TextRange, file: &SourceFile) -> Diagnostic

Convert the violation into a Diagnostic.

impl ViolationMetadata for IOError

fn rule() -> Rule

Returns the rule for this violation

fn explain() -> Option<&'static str>

Returns an explanation of what this violation catches, why it’s bad, and what users should do instead.

fn status() -> RuleStatus

Returns the rule status for this violation.

fn file() -> &'static str

Returns the file where the violation is declared.

fn line() -> u32

Returns the 1-based line where the violation is declared.