Enum askama_warp::Error

#[non_exhaustive]pub enum Error {
    Fmt(Error),
}

askama error type

Feature Interaction

If the feature serde_json is enabled an additional error variant Json is added.

Why not failure/error-chain?

Error from error-chain are not Sync which can lead to problems e.g. when this is used by a crate which use failure. Implementing Fail on the other hand prevents the implementation of std::error::Error until specialization lands on stable. While errors impl. Fail can be converted to a type impl. std::error::Error using a adapter the benefits failure would bring to this crate are small, which is why std::error::Error was used.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

Fmt(Error)

formatting error

Trait Implementations

impl Debug for Error

fn fmt(&self, f: &mut Formatter) -> Result<(), Error>

Formats the value using the given formatter.

impl Display for Error

fn fmt(&self, formatter: &mut Formatter) -> Result<(), Error>

Formats the value using the given formatter.

impl Error for Error

fn cause(&self) -> Option<&dyn Error>

👎 Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn source(&self) -> Option<&(dyn Error + 'static)>

The lower-level source of this error, if any.

fn backtrace(&self) -> Option<&Backtrace>

🔬 This is a nightly-only experimental API. (backtrace)

Returns a stack backtrace, if available, of where this error occurred.

fn description(&self) -> &str

👎 Deprecated since 1.42.0:

use the Display impl or to_string()

if let Err(e) = "xc".parse::<u32>() { // Print e itself, no need for description(). eprintln!("Error: {}", e); }

impl From<Error> for Error

fn from(err: Error) -> Error

Performs the conversion.