KIkillercup·Oct 27, 2015
The (adapted) code from that article was used as a stress test for rustfmt in September: https://github.com/nrc/rustfmt/issues/296
In Good Practices for Writing Rust Librariesnrc
rustfmt
Rust2015–2015
nrc / rustfmt
rustfmt
Format Rust code
3Distinct people
3Mentions
0Explicit recommenders
9GitHub stars
What to know before exploring
What it is
Format Rust code
GitHub
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, 12:54:37 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 week3 dated mentions
Observed mentions: 2015-09-09 16:30:43 UTC to 2015-10-27 08:07:00 UTC. Weeks start Monday, 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 |
|---|---|---|---|---|---|
| Sep 7 | 2015-09-07 00:00:00 UTC | 2015-09-14 00:00:00 UTC | 1 | 0 | 1 |
| Sep 14 | 2015-09-14 00:00:00 UTC | 2015-09-21 00:00:00 UTC | 0 | 0 | 0 |
| Sep 21 | 2015-09-21 00:00:00 UTC | 2015-09-28 00:00:00 UTC | 0 | 0 | 0 |
| Sep 28 | 2015-09-28 00:00:00 UTC | 2015-10-05 00:00:00 UTC | 0 | 0 | 0 |
| Oct 5 | 2015-10-05 00:00:00 UTC | 2015-10-12 00:00:00 UTC | 0 | 0 | 0 |
| Oct 12 | 2015-10-12 00:00:00 UTC | 2015-10-19 00:00:00 UTC | 0 | 0 | 0 |
| Oct 19 | 2015-10-19 00:00:00 UTC | 2015-10-26 00:00:00 UTC | 0 | 0 | 0 |
| Oct 26 | 2015-10-26 00:00:00 UTC | 2015-11-02 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
3 sourcesServo doesn't mandate that style. We use a mix of column-aligned and shifted styles. We tend to column align a lot, but we're okay with other ways of aligning as long as it doesn't exceed 120 characters.
> It's the presumption behind these kind of rigid code reformatters.
Rustfmt isn't rigid!
It's highly configurable, file a bug if you want this sort of formatting to be a part of the configuration. I've already filed an issue that asks for a less aggressive line-splitter https://github.com/nrc/rustfmt/issues/448
In Good Practices for Writing Rust Libraries> 80% of Crates.io runs on stable, it really depends on exactly what you're doing.
While this is probably factually true -- I've had quite the opposite experience. :(
- I want to write benchmarks for my code, but I need `#[feature(test)]` AKA nightly.
- I want to [format my Rust code](https://github.com/nrc/rustfmt), but I need nightly.
- I want to use Huon Wilson's SIMD crate, which requires nightly.
I'm not saying these things should be stable right now, but I am saying if you try to use Rust right now you _will_ encounter a lot of stuff marked as unstable and/or only usable on nightly due to XYZ. I still think Rust is amazing and everyone should give it a shot though, but it's not as stable/polished experience as I think it will be in say a year from now. The language is stable, but the ecosystem just isn't yet.
P.S. You've helped me p
Read the rest
ersonally all too much over the Rust IRC channel, so thank you a million times for that! :)