mirror of
https://github.com/notohh/rustlings.git
synced 2024-12-23 11:48:09 -05:00
f714534393
info.toml: ```toml [[exercises]] name = "threads3" path = "exercises/threads/threads3.rs" mode = "test" hint = """ An alternate way to handle concurrency between threads is to use a mpsc (multiple producer, single consumer) channel to communicate. With both a sending end and a receiving end, it's possible to send values in one thread and receive them in another. Multiple producers are possible by using clone() to create a duplicate of the original sending end. See https://doc.rust-lang.org/book/ch16-02-message-passing.html for more info. """ ``` threads3'hint contains this link, so it should be placed in Further Information
10 lines
641 B
Markdown
10 lines
641 B
Markdown
# Threads
|
|
|
|
In most current operating systems, an executed program's code is run in a process, and the operating system manages multiple processes at once.
|
|
Within your program, you can also have independent parts that run simultaneously. The features that run these independent parts are called threads.
|
|
|
|
## Further information
|
|
|
|
- [Dining Philosophers example](https://doc.rust-lang.org/1.4.0/book/dining-philosophers.html)
|
|
- [Using Threads to Run Code Simultaneously](https://doc.rust-lang.org/book/ch16-01-threads.html)
|
|
- [Using Message Passing to Transfer Data Between Threads](https://doc.rust-lang.org/book/ch16-02-message-passing.html)
|