-
Notifications
You must be signed in to change notification settings - Fork 100
Consider switching to official rust style (rustfmt zinc) #358
Comments
For reference, previous discussion. TL;DR: This would 🔪 |
@mcoffin. You're right of course on I think (and hope?) the cognitive dissonance of a unique style is likely to only increase over time as the standard style becomes more and more standard (e.g. I bet IDEs will not even make much of the style for Rust code configurable). |
Don't get me wrong, I'm all for it. Gonna be some work for somebody though. And yea... we need to have an RFC party or something... |
This might be best tackling when splitting things into new repos. I think
@farcaller mentioned this in the last 24hrs.
Have we removed all the `#ignore doc_comments` yet too?
|
I'm all in for it, but is rustfmt stable enough now? |
@farcaller It's pretty good but you still need to look at the diffs to keep things in check. I ran it on a few of my projects the other day with pretty good results. |
Touches nose On a more serious note, I don't know what it does with your macros, but we'd have to watch the |
I want to kill |
Like I said earlier and on IRC, we need to have an RFC party and make some tech decisions so that we can start working towards common goals. |
Makes sense. Let me fire up a dedicated ticket for that. |
Putting out a feeler. I think using the standard style is probably a good idea and makes contributing easier (in addition to making my emacs configuration easier).
https://github.com/rust-lang/rust/tree/master/src/doc/style
rustfmt can probably do a majority of the work, although it still needs some handholding in my experience to prevent it from going in the weeds in edge cases. With
cargo install
we can berustfmt
ing in no time.I don't think there are too many major outstanding PRs that would need to be reworked, so now seems as good a time as any to make the switch if this suggestion is amenable.
The text was updated successfully, but these errors were encountered: