GUguycook·Jan 28, 2017
And if compile times are getting you down, you can still get the checks without producing a binary and save quite a bit of time with https://github.com/rsolomo/cargo-check
In Ask HN: How do I understand Rust?rsolomo
cargo-check
Rust2017–2017
rsolomo / cargo-check
cargo-check
Discover this repository through its Hacker News conversations.
2Distinct people
2Mentions
0Explicit recommenders
97GitHub stars
What to know before exploring
What it is
A public description has not been verified.
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM 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 day2 dated mentions
Observed mentions: 2017-01-19 00:02:30 UTC to 2017-01-28 01:59:22 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 |
|---|---|---|---|---|---|
| Jan 19 | 2017-01-19 00:00:00 UTC | 2017-01-20 00:00:00 UTC | 1 | 0 | 1 |
| Jan 20 | 2017-01-20 00:00:00 UTC | 2017-01-21 00:00:00 UTC | 0 | 0 | 0 |
| Jan 21 | 2017-01-21 00:00:00 UTC | 2017-01-22 00:00:00 UTC | 0 | 0 | 0 |
| Jan 22 | 2017-01-22 00:00:00 UTC | 2017-01-23 00:00:00 UTC | 0 | 0 | 0 |
| Jan 23 | 2017-01-23 00:00:00 UTC | 2017-01-24 00:00:00 UTC | 0 | 0 | 0 |
| Jan 24 | 2017-01-24 00:00:00 UTC | 2017-01-25 00:00:00 UTC | 0 | 0 | 0 |
| Jan 25 | 2017-01-25 00:00:00 UTC | 2017-01-26 00:00:00 UTC | 0 | 0 | 0 |
| Jan 26 | 2017-01-26 00:00:00 UTC | 2017-01-27 00:00:00 UTC | 0 | 0 | 0 |
| Jan 27 | 2017-01-27 00:00:00 UTC | 2017-01-28 00:00:00 UTC | 0 | 0 | 0 |
| Jan 28 | 2017-01-28 00:00:00 UTC | 2017-01-29 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesA symbiotic relationship is an apt way to phrase it. Most of my invocations of rustc aren't even to actually compile an executable. Typically I'm running something akin to a cargo-check[1] to ask rustc some questions about my codebase: What type did you infer for this binding? Are these generic bounds precise enough? How long can I keep this reference around?
In C++ I loathe generic programming, a template instantiation error is something I fear. Whereas in Rust I knowingly compile broken generic code all the time, because the errors are (usually) good enough to help me fix it.
[1]: https://github.com/rsolomo/cargo-check
In Rust vs. Go