Completing rustfmt and the Rust style guidelines

[burntsushi]

Note that while gofmt (and Go) has strong opinions on a lot of things, there is no hard rule about line length in the Go community as far as I’m aware. I’m an 80 column zealot, so I’ve always written Go in 80 columns and I use gofmt with no problems. I don’t see any reason why rustfmt couldn’t take a similarly unopinionated position.

[oli-obk]

I think it would be trivial to force rustfmt to never exceed 80 columns if it didn’t have more than 80 before reformatting. Making it take less than 80 if you have more than 80 should be a no-no since it could be that the programmer wants to be bounded by 100.

[burntsushi]

Yes. This is exactly what I’m hoping will happen.

[phaylon]

Then fight to make the default rustfmt standard nice to read for you. In particular, don’t fight about everything, fight about what really is important to you (what would make rustfmt completely unusable in your situation).

I’m already aware that many people disagree with my style. You’re also excluding everybody in the “fight” that comes to Rust after rustfmt is done.

Seriously, if every single project I’ve been in was able to agree on style, we can agree on a single style for rustfmt too!

Even if this style is not perfect to each one of us, as long as it is usable, we’ll be able to live with it. Every developer is able to adapt to different styles on different projects.

If the above is true, where is the problem with a per-project configuration file? For you, there wouldn’t even be more work. For your new projects, rustfmt could just use the default style guide settings. For others’ projects with customizations, rustfmt will pick up the configuration by itself and you invoke it no different.

I still find it’s a good compromise.

[system]

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.