linejudge 0.3.0

The test corpus and engine that check line-of-code counters against their own declared rules
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

//! Several things wrong at once, which is what reading a corpus or a set of rules finds.

use std::error::Error;
use std::fmt;
use std::ops::Deref;

/// Everything wrong with what was read, in the order it was found. Reading stops at nothing, so a
/// corpus with three broken cases names all three instead of the first.
///
/// It prints one fault per line and is a [`std::error::Error`], so `?` carries it into a
/// `Box<dyn Error>` the way any other error does. It also derefs to a slice, so the faults can be
/// walked, counted and joined as they could when this was a plain vector.
#[derive(Debug)]
pub struct Faults(Vec<String>);

impl Deref for Faults {
    type Target = [String];

    fn deref(&self) -> &[String] {
        &self.0
    }
}

impl fmt::Display for Faults {
    fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
        f.write_str(&self.0.join("\n"))
    }
}

impl Error for Faults {}

impl From<Vec<String>> for Faults {
    fn from(faults: Vec<String>) -> Faults {
        Faults(faults)
    }
}

impl From<String> for Faults {
    fn from(fault: String) -> Faults {
        Faults(vec![fault])
    }
}