pub enum ISOError {
Io(Error),
Utf8(Utf8Error),
Utf16,
InvalidFs(&'static str),
ParseInt(ParseIntError),
TryFromInt(TryFromIntError),
ReadSize(usize),
VerboseNom(VerboseError<Vec<u8>>),
}
Expand description
The master error structure.
Variants§
Io(Error)
I/O error while trying to read the filesystem image.
Utf8(Utf8Error)
String value that was expected to fit into a UTF-8 shape, in fact did not. This is not the greatest design decision as nothing in ISO 9660 / ECMA-119 should be encoded in UTF-8.
Utf16
encoding-rs
ran into one or more errors parsing the string. Joliet only.
InvalidFs(&'static str)
The filesystem contained error(s) and could not be parsed.
ParseInt(ParseIntError)
A String
that was supposed to contain a numeric value did not. Currently this error only occurs in the file identifier parsing code.
TryFromInt(TryFromIntError)
An error trying to go from one size of integer to another.
ReadSize(usize)
The buffer or block did not have enough data. Presumably the filesystem is corrupt.
See Also
VerboseNom(VerboseError<Vec<u8>>)
A nom
parser failed. Most likely the filesystem is either corrupt. This is the verbose
variant. If you don’t need the extra context that nom’s VerboseError
type brings,
disabling the verbose-error
feature will utilize the standard nom error type.