Rain (sunshowers)
sunshowers.io · Personal blog · on HN since 2020
Rain is a Rust developer and author of cargo-nextest who writes about async Rust, Unix signals, type systems, and hardware.
What HN saysHN commenters recommend her posts on async cancellation and cancel safety, and the nextest and Tokio post, calling the Tokio mutex section especially interesting.
17HN people shared it
6linked it in comments
19stories submitted
956story points
11 months agolast shared
2020people per year2026
Most-shared posts
- 1Cancellations in async Rust4 people · 240 points · first shared 2025 · 89 comments on HN
- 2Demystifying monads in Rust through property-based testing4 people · 24 points · first shared 2025 · 2 comments on HN
- 3ECC RAM on AMD Ryzen 7000 Desktop CPUs3 people · 2 points · first shared 2023 · discussion on HN
- 4Debugging a rustc segfault on Illumos2 people · 247 points · first shared 2024 · 58 comments on HN
- 5Beyond Ctrl-C: The dark corners of Unix signal handling2 people · 181 points · first shared 2024 · 71 comments on HN
- 6Why Rust nextest is process-per-test2 people · 122 points · first shared 2025 · 35 comments on HN
- 7Open and closed universes (2021)2 people · 27 points · first shared 2024 · 4 comments on HN
- 8The social consequences of type systems2 people · 3 points · first shared 2020 · 1 comments on HN
- 9How (and why) nextest uses tokio, part 12 people · 2 points · first shared 2022 · discussion on HN
- 10Nextest and tokio2 people · first shared 2024
- 11In defense of lock poisoning in Rust1 people · 60 points · first shared 2025 · 6 comments on HN
- 12SocketAddrV6 is not roundtrip serializable1 people · 47 points · first shared 2025 · 14 comments on HN
- 13Thinking about Dependencies1 people · 1 points · first shared 2022 · discussion on HN
- 14There is no free will1 people · first shared 2025
- 15About1 people · first shared 2025
What HN people wrote when they linked it
foresterre · 2025-10-04
Rain showed that not all may be as simple as it seems to do it correctly.
In her presentation on async cancellation in Rust, she spoke pretty extensively on cancel safety and correctness, and I would recommend giving it a watch or read.
https://sunshowers.io/posts/cancelling-async-rust/
sunshowers · 2025-10-03
Author here -- I'd recommend reading my blog post about how cargo-nextest uses Tokio + async Rust to handle very complex state machines: https://sunshowers.io/posts/nextest-and-tokio/
mwcampbell · 2025-11-01
In the spirit of "every non-trivial program will expand until ...", I think preemptively choosing async for anything much more complex than a throwaway script might be justified. In this case, the relevant thing isn't performance or expected number of concurrent users/connections, but whether the program is likely to become or include a non-trivial state machine. My primary influence on this topic is this post from @sunshowers: https://sunshowers.io/posts/nextest-and-tokio/
AceJohnny2 · 2025-10-03
> He writes
They go by they/she
https://sunshowers.io/about/
foota · 2025-10-03
https://sunshowers.io/posts/cancelling-async-rust/#the-pain-of-tokio-m… was the most interesting part of this for me, as I can totally see making mistakes like this.
steve_rambo · 2024-05-08
ECC is fully supported by consumer AMD processors (at least Ryzen 7000, and I think earlier ones too). You need to pick a matching motherboard, most boards from ASRock will do. And you need to find unbuffered ECC RAM, this is more difficult than the previous two and is why I had to give up on the whole idea.
Related post:
https://sunshowers.io/posts/am5-ryzen-7000-ecc-ram