Commit graph

10 commits

Author SHA1 Message Date
mo8it
dfa2b44f71 threads2 solution 2024-07-01 11:11:11 +02:00
mo8it
b000164eed threads1 solution 2024-07-01 10:59:33 +02:00
mo8it
7cdf6b7942 Add missing semicolons 2024-05-22 15:13:18 +02:00
mo8it
0a2d4dae5a Merge branch 'main' 2024-04-24 15:48:29 +02:00
mo8it
2f810a4da6 Clean up and unify exercises 2024-04-17 23:34:27 +02:00
mo8it
fa1f239a70 Remove "I AM NOT DONE" and the verify mode and add AppState 2024-04-11 02:51:02 +02:00
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
mo8it
842e341895 threads2: simplify threads2 2024-03-27 21:24:36 +01:00
mo8it
71700c506c Remove unneeded Arc 2024-03-18 01:12:37 +01:00
Adam Brewer
64d95837e9 Update Exercises Directory Names to Reflect Order 2023-10-16 07:37:12 -04:00