1
0
Fork 0
mirror of https://github.com/rust-lang/rustlings.git synced 2024-05-09 12:16:10 +02:00
rustlings/exercises/20_threads
YunShu f714534393
docs: add more info in threads
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
2024-04-08 22:07:26 +08:00
..
README.md docs: add more info in threads 2024-04-08 22:07:26 +08:00
threads1.rs Update Exercises Directory Names to Reflect Order 2023-10-16 07:37:12 -04:00
threads2.rs threads2: simplify threads2 2024-03-27 21:24:36 +01:00
threads3.rs Remove unneeded Arc 2024-03-18 01:12:37 +01:00

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