corona 0.4.3

Coroutine and Async/Await support for tokio-based futures
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

//! Various errors.

use std::any::Any;
use std::error::Error;
use std::fmt::{self, Display, Formatter};

pub use context::stack::StackError;

/// An error marker when a future is dropped before having change to get resolved.
///
/// If you wait on a future and the corresponding executor gets destroyed before the future has a
/// chance to run, this error is returned as there's no chance the future will ever get resolved.
/// It is up to the waiter to clean up the stack, or use methods that panic implicitly.
#[derive(Debug, Eq, PartialEq, Ord, PartialOrd, Hash)]
pub struct Dropped;

impl Error for Dropped {
    fn description(&self) -> &str {
        "The future waited on has been dropped before resolving"
    }
}

impl Display for Dropped {
    fn fmt(&self, f: &mut Formatter) -> fmt::Result {
        write!(f, "{}", self.description())
    }
}

/// The task (coroutine) has failed.
///
/// This is used as an error type and represents an unsuccessful coroutine.
#[derive(Debug)]
pub enum TaskFailed {
    /// There was a panic inside the coroutine.
    ///
    /// The coroutine panicked and it was spawned with
    /// [`spawn_catch_panic`](../coroutine/struct.Coroutine.html#method.spawn_catch_panic).
    Panicked(Box<Any + Send + 'static>),
    /// There was a panic in the coroutine.
    ///
    /// However, the panic got re-established inside the coroutine's caller. Observing this result
    /// is rare, since usually the propagated panic destroys the owner of the coroutine as well.
    PanicPropagated,
    /// The coroutine was lost.
    ///
    /// This can happen in case the executor the coroutine was spawned onto was dropped before the
    /// coroutine completed.
    ///
    /// Technically, the coroutine panicked, but this special panic is handled differently.
    Lost,
}

impl Error for TaskFailed {
    fn description(&self) -> &str {
        match *self {
            TaskFailed::Panicked(_) | TaskFailed::PanicPropagated => "The coroutine panicked",
            TaskFailed::Lost => "The coroutine was lost",
        }
    }
}

impl Display for TaskFailed {
    fn fmt(&self, f: &mut Formatter) -> fmt::Result {
        write!(f, "{}", self.description())
    }
}