231bc3cc46
The use case is as follows: let's say I have a scheduler that uses libfringe for context switching. A single thread may open several sockets, each of which presents a std::io::Read interface, and waiting in Read::read requires having a reference to the yielder inside the socket. This could be worked around with RefCell in the API consumer, but there is no real reason to not implement it in libfringe. close #48 |
||
|---|---|---|
| .. | ||
| arch | ||
| debug | ||
| os | ||
| context.rs | ||
| generator.rs | ||
| lib.rs | ||
| owned_stack.rs | ||
| slice_stack.rs | ||
| stack.rs | ||