STsteveklabnik·Nov 28, 2020
"rustlings" is already a well-known project within Rust world https://github.com/rust-lang/rustlings
In AWS hires Rust compiler team co-lead Felix Klockrust-lang
rustlings
Rust2016–2025
rust-lang / rustlings
rustlings
:crab: Small exercises to get you used to reading and writing Rust code!
46Distinct people
53Mentions
2Explicit recommenders
64.7KGitHub stars
What to know before exploring
What it is
:crab: Small exercises to get you used to reading and writing Rust code!
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
If you prefer learning by doing, I recommend rustlings. Its a bunch of small exercises that roughly follow the content of the main rust book. https://github.com/rust-lang/rustlings
jocaal used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:53 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year53 dated mentions
Observed mentions: 2016-02-02 09:17:13 UTC to 2025-07-07 13:32:51 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 16 | 3 | 13 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
8 sourcesI found the following two resources to be excellent for rust teething issues:
Rustlings: A set of exercises to "fix" to get you used to compiler error messages. https://github.com/rust-lang/rustlings
Rust by example: A collection of short runnable examples to get you familiar with the standard library. https://doc.rust-lang.org/stable/rust-by-example/
In Fighting Rust's Expressive Type SystemI like this one https://github.com/rust-lang/rustlings. It is a set of exercises in which you must fix fragments of the code to pass the test.
In Ask HN: How to Learn RustYou could try this: https://github.com/rust-lang/rustlings
In Rust 1.46Small exercises to get you used to reading and writing Rust code
2 points · Open discussionHi Amasad! I almost replied to my own comment yesterday after I discovered that the rustlings readme[0] now has a link to "Run on repl.it"[1] (as well as Gitpod). Evidently this was added ~11 days ago[2]...although I personally thought it would be a more complicated solution than just configuring the .replit file correctly in the rustlings repo. I had independently come up with the same solution to make the 'Run' button rebuild the .cargo but it felt too 'hacky' for me to accept as a final product and suggest to the rustlings team.
0: https://github.com/rust-lang/rustlings
1: https://repl.it/github/rust-lang/rustlings
2: https://github.com/rust-lang/rustlings/pull/471
A couple of months ago my friends and I tried to get rustlings working in repl.it . I really, really wish I had documented those efforts thoroughly but at the time it was ju
Read the rest
st an exploratory deep-dive to determine if I should follow up with documentation of issues and more detail, and I decided against using my time for that...kind of regret that now.
Three issues I remember facing:
A) inode not updating in the shell even when files changed in the GUI editor. [seems improved now]
B) /home/runner/.cargo/ (and some other supporting directories i think) disappearing after some time / series of actions and-or inaction [today only via inactivity?]
C) At some point we realized the shell wasn't a 'real' shell but I can't remember what led us to this conclusion, just that it got in our way when debugging the above issues.
(A) [Basically fixed already] What I remember is that the repl.it shell environment, while being extremely high fidelity, seemed to have some idiosyncracies in the way the filesystem worked vs a typical bare-metal OS. Two months ago I had trouble where 'rustlings verify' worked okay but 'rustlings watch' wouldn't notice that a file had been edited. Oddly enough, any shell command investigation would also report that the file hadn't been edited/modified recently, but 'cat file.rs' would still output the saved changes.
(B) [Partially fixed, still an "issue" due to long re-builds but not hard blocker] /home/runner/.cargo disappears after any inactivity. This seems more predictable now than I remember it two months ago - two months ago I might only be able to run 'rustlings watch' once and then very shortly after, the shell would no longer be able to find the rustlings binary anymore and I'd have to rebuild from scratch. Generally there were some errors whenever rebuilding, so the solution for me was typically to create a whole new repl.it from scratch and do the initial build. I don't remember what errors caused the "need" for a new repl.it from scratch every time I needed to rebuild it. This still seems like an "issue", sort of, that the rustlings .replit file has a workaround for which works reasonably well and I suspect this behavior is fairly necessary for repl.it the business. But the binaries still disappear after a short inactive period and need to be rebuilt which takes quite some time on the free tier (10+ min?).
(C) [null, and generally not an "issue"] No memory of what behavior caused us to give the shell the moniker "poverty shell" but overall I've generally found the repl.it shells to be extremely high fidelity such that I generally don't realize I'm using a slightly handicapped system. However, this seems to have changed for python shells...now I seemed locked into something like IPython and can't get to a linux shell via exit(), ctrl-D, etc. Maybe this was always the case and I only remember using the linux shell in the C/C++/Rust repl's.
0: https://github.com/rust-lang/rustlings
1: https://repl.it/github/rust-lang/rustlings
2: https://github.com/rust-lang/rustlings/pull/471
I've wanted to turn some students onto Rust, so I tried to give them https://github.com/rust-lang/rustlings loaded into a repl.it account -- but the way repl.it works breaks rustlings in multiple ways.
I'd love if this Rust playground could eventually provide that experience.
In Rust PlaygroundIf you are more of an interactive learner I would recommend installing rust on your machine and then cloning the rustlings repo https://github.com/rust-lang/rustlings.
Rustlings is an interactive collection of rust exercises that are either incorrect or incomplete. The exercises are grouped into key concepts of rust and cross referenced with relevant chapters in the rust book https://doc.rust-lang.org/book/
The general flow is to open up the given chapter of the rust book for a set of exercises and hack away at them until they compile. It's a good way to quickly get an introduction to rust and its core features.
In Rust Lang in a nutshell