pub enum Error {
}
Expand description
This is the error type used in fasteval
’s Result
s.
For performance reasons, fasteval
makes an effort to always return Error
s
instead of using panic!()
.
Variants§
SlabOverflow
Too many Expressions/Values/Instructions were stored in the Slab.
A Slab is pre-allocated at the beginning of the process, and it is
not re-sized. You can use Slab::with_capacity()
to increase the
number of items that can be stored.
AlreadyExists
Returned by EvalNamespace::create_cached()
.
An entry with the same name already exists in the Namespace. If you intend to overwrite existing entries, use EvalNamespace::set_cached()` instead.
EOF
Reached an unexpected End Of Input during parsing.
EofWhileParsing(String)
Reached an unexpected End Of Input during parsing.
The String
field contains information about what was being parsed
when the EOF was reached.
Utf8ErrorWhileParsing(String)
UTF8 decoding error.
The String
field contains information about what was being parsed
when the UTF8 error occurred.
TooLong
The expression string input was too long.
This is a safety check that prevents malicious inputs that would be expensive to parse.
TooDeep
The expression was too recursive.
This is a safety check that prevents malicious inputs that would be expensive to parse.
UnparsedTokensRemaining(String)
An expression was parsed, but there is still input data remaining.
The String
field contains the un-parsed input data.
InvalidValue
A value was expected, but invalid input data was found.
ParseF64(String)
An error occurred during the parsing of a f64 number.
The String
field contains the data that caused the error.
Expected(String)
The expected input data was not found.
The String
field tells you what was expected.
WrongArgs(String)
A function was called with the wrong arguments.
The String
field contains information about the expected arguments.
Undefined(String)
The expression tried to use an undefined variable/function.
You can define variables/functions with a Namespace.
Unreachable
This error should never occur because it is only produced by code paths
that should never execute. This is more performant than using the
unreachable!()
macro.