Archives
/
rustlings
mirror of https://github.com/rust-lang/rustlings
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
v6
main
gh-pages
1.0.0
1.0.1
1.1.0
1.1.1
1.2.0
1.2.1
1.2.2
1.3.0
1.4.0
1.4.1
1.5.0
1.5.1
2.0.0
2.1.0
2.2.0
2.2.1
3.0.0
4.0.0
4.1.0
4.2.0
4.3.0
4.4.0
4.5.0
4.6.0
4.7.0
4.7.1
4.8.0
5.0.0
5.1.0
5.1.1
5.2.0
5.2.1
5.3.0
5.4.0
5.4.1
5.5.0
5.5.1
5.6.0
5.6.1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
rustlings/exercises/20_threads
History
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
 		1 month ago
..
README.md docs: add more info in threads 1 month ago
threads1.rs Update Exercises Directory Names to Reflect Order 7 months ago
threads2.rs threads2: simplify threads2 2 months ago
threads3.rs Remove unneeded Arc 2 months ago

README.md

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