diff options
| author | bors <bors@rust-lang.org> | 2014-01-28 00:41:30 -0800 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2014-01-28 00:41:30 -0800 |
| commit | 3781728d8f0e506048aef394ed02c668383c3027 (patch) | |
| tree | 98f1beb0f2267649985f581c90638bf94e3abc5d | |
| parent | 1fdd23166d4b0d7791111b8067fec38d711c79c5 (diff) | |
| parent | f5723791e910381cebcbdde84575450898074795 (diff) | |
| download | rust-3781728d8f0e506048aef394ed02c668383c3027.tar.gz rust-3781728d8f0e506048aef394ed02c668383c3027.zip | |
auto merge of #11837 : xales/rust/doc-fixes, r=cmr,huonw,alexcrichton
| -rw-r--r-- | doc/guide-runtime.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/guide-runtime.md b/doc/guide-runtime.md index d4ffb4c1155..fa5a2b23ca8 100644 --- a/doc/guide-runtime.md +++ b/doc/guide-runtime.md @@ -176,7 +176,7 @@ implemented in user-space. The primary concern of an M:N runtime is that a Rust task cannot block itself in a syscall. If this happens, then the entire OS thread is frozen and unavailable for running more Rust tasks, making this a (M-1):N runtime (and you can see how -this can reach 0/deadlock. By using asynchronous I/O under the hood (all I/O +this can reach 0/deadlock). By using asynchronous I/O under the hood (all I/O still looks synchronous in terms of code), OS threads are never blocked until the appropriate time comes. |