Rust的任务与通信（翻译）.docVIP

Rust Tasks and Communication Tutorial（翻译） 目录 1 Introduction（介绍） 2 Basics（基础） 3 Handling task failure（处理任务失败） 1. Introduction（介绍） The designers of Rust designed the language from the ground up to support pervasive and safe concurrency through lightweight, memory-isolated tasks and message passing.（Rust设计者从头开始通过轻量级、内存隔离的任务和消息传递支持普适和安全的并发。） Rust tasks are not the same as traditional threads: rather, they are more like green threads.（Rust任务和传统的线程不同：相对的，它们更像绿色线程。） The Rust runtime system schedules tasks cooperatively onto a small number of operating system threads.（Rust的运行时系统将协作的任务调度到很少的操作系统线程上。） Because tasks are significantly cheaper to create than traditional threads, Rust can create hundreds of thousands of concurrent tasks on a typical 32-bit system.（因为任务比创建传统线程廉价得多，Rust可以在典型的32位系统创建成千上万的并发任务。） Tasks provide failure isolation and recovery.（任务提供失败隔离和恢复。） When an exception occurs in Rust code (as a result of an explicit call to fail!(), an assertion failure, or another invalid operation), the runtime system destroys the entire task.（当Rust代码出现异常（），运行时系统销毁整个任务。） Unlike in languages such as Java and C++, there is no way to catch an exception.（和Java和C++这些语言不同，没有办法捕获异常。） Instead, tasks may monitor each other for failure.（作为代替，任务可以互相监视失败。） Rust tasks have dynamically sized stacks.（Rust任务拥有动态大小的栈。） A task begins its life with a small amount of stack space (currently in the low thousands of bytes, depending on platform), and acquires more stack as needed.（一个栈以很少量的栈空间开始（根据平台，现在低致几千字节），当需要时获得更多。） Unlike in languages such as C, a Rust task cannot run off the end of the stack.（不像C语言，Rust的任务不可能跳过栈底。） However, tasks do have a stack budget.（然而，任务有栈预算。） If a Rust task exceeds its stack budget, then it will fail safely: with a checked exception.（如果Rust任务超出栈预算，将安全的失败：使用检查的异常。） Tasks use Rusts type system to provide strong memory safety guarantees.（任务使用Rust的类型系统来提供强健的内存安全保障。） In particular, the type system guarantees that tasks cannot share mutable state with each other.（特别的，类型系统保证任务不能互