[−][src]Enum askama_shared::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
Fmt(Error)
formatting error
Trait Implementations
impl Debug for Error
[src]
impl Display for Error
[src]
impl Error for Error
[src]
fn description(&self) -> &str
[src]
fn cause(&self) -> Option<&dyn ErrorTrait>
[src]
fn source(&self) -> Option<&(dyn Error + 'static)>
1.30.0[src]
fn backtrace(&self) -> Option<&Backtrace>
[src]
impl From<Error> for Error
[src]
Auto Trait Implementations
impl RefUnwindSafe for Error
impl Send for Error
impl Sync for Error
impl Unpin for Error
impl UnwindSafe for Error
Blanket Implementations
impl<T> Any for T where
T: 'static + ?Sized,
[src]
T: 'static + ?Sized,
impl<T> Borrow<T> for T where
T: ?Sized,
[src]
T: ?Sized,
impl<T> BorrowMut<T> for T where
T: ?Sized,
[src]
T: ?Sized,
fn borrow_mut(&mut self) -> &mut T
[src]
impl<T> From<T> for T
[src]
impl<T, U> Into<U> for T where
U: From<T>,
[src]
U: From<T>,
impl<T> ToString for T where
T: Display + ?Sized,
[src]
T: Display + ?Sized,
impl<T, U> TryFrom<U> for T where
U: Into<T>,
[src]
U: Into<T>,
type Error = Infallible
The type returned in the event of a conversion error.
fn try_from(value: U) -> Result<T, <T as TryFrom<U>>::Error>
[src]
impl<T, U> TryInto<U> for T where
U: TryFrom<T>,
[src]
U: TryFrom<T>,