Getting result from coroutines

[3Hren]

Hi!

Are you planning to add an ability to extract results from finished coroutines, like it is implemented in Thread?

Something like this:

let coro = Coroutine::spawn(move || {
    42
});

let res = coro.join().unwrap();
assert_eq!(42, res);

[zonyitoo]

Then, what's the return type of resume? Result<Option<T>>?

If the parent and its children are not running in the same thread, then the return result must be transferred from this thread to another thread. This is also an obstacle of implementing #48 .

[3Hren]

Hmm, good catch. Then, this issue seems like a subset of #48.

[therustmonk]

With #68 it's possible:

let mut coro = Coroutine::spawn(move |me,_| {
    42
});
let result = coro.resume(0);

We haven't return types larger than usize. For custom types pointers have to be used, like I do there. If we add something like Result<T> we'll increase overhead for coroutines which don't need results quite.

I think this issue should be closed.

[zonyitoo]

You are right.