EopParseError

Defined in: error.rs:12

Available on crate feature alloc only.

pub enum EopParseError {
    InvalidLine { line: usize, reason: &'static str },
    InvalidNumber { line: usize, column: &'static str, value: alloc::string::String },
    Empty,
    NonMonotonicMjd { line: usize, previous: f64, current: f64 },
    Table(EopLookupError),
}

Error during EOP data file parsing.

#[non_exhaustive]: a downstream exhaustive match would otherwise break on every variant added here. Use a wildcard arm.

Variants

InvalidLine

line: usize reason: &‘static str

A line could not be parsed.

---

InvalidNumber

line: usize column: &‘static str value: alloc::string::String

A numeric field could not be parsed.

---

Empty

The file contained no valid entries.

---

NonMonotonicMjd

line: usize previous: f64 current: f64

MJD values are not monotonically increasing.

---

Table

Table(EopLookupError)

The rows parsed, and building the table from them was refused. The parser checks the line-level rules itself, so reaching this means the two disagree — reported rather than folded into Self::Empty, which would say the file held no rows at all.

---