foundation.rust-lang.org VS rustfmt

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

This is why some of the bigger programming languages have a consortium behind them, dedicated to maintaining the language and making decisions for its continued improvement. When you look at the logos at the bottom of the Rust Foundation page, you can see some pretty big names.

The Rust foundation, which is a nonprofit general (delaware) corporation with bylaws, employees, a normal legal existence. It owns the trademarks and domain names, acts as a legal and administrative point of contact when one is needed, and has I think operational and funding responsibility for infrastructure (crates.io, CI, etc.) The foundation has members which are almost all corporate sponsors who donate money (and sometimes people) to further its mandate. There's a fairly broad set of companies involved here: Microsoft, Google, Amazon, Meta, Huawei, etc. etc.

When you say enterprise, who do you mean? Rust is absolutely being pushed by faang et al for example. Just look at the bottom of the Rust foundation page[0]. You do not see this support for things like Nim or Julia[1].

[0] https://foundation.rust-lang.org/

The Rust language is supported by the Rust Foundation, more details on that website. Financial donors to the Rust Foundation are about 30-40 companies currently, the bigger ones include Mozilla, Google, Microsoft, AWS, and Meta

> https://foundation.rust-lang.org/ 15,000

With all due respect, they don't need this money. Rust is a great project, and deserving, but they already have plenty of sponsors.

I would have rather seen 150 x $100 go to smaller projects. So much great software is being written, by people who are barely scraping by, and even $100 could be the motivation for someone to finish something widely useful.

So, let's clarify a couple things first about how the Rust and Cargo crates work. First off, there is no single company or entity who's the sole contributor to the core Rust tooling. Rust is an open source project to which anyone can view the codebase and contribute (though there's a select set of people who are responsible for approving changes to it and managing releases). It's worth noting this doesn't mean there isn't an organization responsible for the project however. The Rust Foundation are a non-profit who manages the core repositories and tooling, and is also responsible for setting high level goals for the language.

I don't think it is the same as Java. There is no single company owning Rust. Several big companies are investing in rust foundation (https://foundation.rust-lang.org/) including Google in particular which had quite a story regarding Java.

Recently, several big techs like Google, Microsoft, Mozilla and Amazon jointly launched a non-profit organization to help the language maintain itself by giving full support to the maintainers who lead and develop the project. Here at Vaultree we use Rust in our product and services, as we need to deliver data with reliability and agility to our customers, as we are in a business line where any error or inaccuracy can be costly, the adoption of Rust was a great fit for us.

The author provides very surface-level criticism of two Rust tools, but they don't look into why those choices were made.

With about five minutes of my time, I found out:

wrap_comments was introduced in 2019 [0]. There are bugs in the implementation (it breaks Markdown tables), so the option hasn't been marked as stable. Progress on the issue has been spotty.

--no-merge-sources is not trivial to re-implement [1]. The author has already explained why the flag no longer works -- Cargo integrated the command, but not all of the flags. This commit [2] explains why this functionality was removed in the first place.

Rust is open source, so the author of this blog post could improve the state of the software they care about by championing these issues. The --no-merge-sources error message even encourages you to open an issue, presumably so that the authors of Cargo can gauge the importance of certain flags/features.

You could even do something much simpler, like adding a comment to the related issues mentioning that you ran into these rough edges and that it made your life a little worse, or with a workaround that you found.

Alternatively, you can continue to write about how much free software sucks.

[0]: https://github.com/rust-lang/rustfmt/issues/3347

[1]: https://github.com/rust-lang/cargo/pull/10344

[2]: https://github.com/rust-lang/cargo/commit/3842d8e6f20067f716...

The new style still supports single line let-else, and there is a configuration parameter to make it be on one line also for longer lines.

It seems there is an issue about this dating all the way back from 2018 but yet it still hasn't been fixed.

However since 4179 recent versions should merge configuration files. Not sure what the details / specifics are but if just ignoring the file entirely is not good enough you might give it its own directory and rustfmt.toml file and see if that works.

Could this be be #3863 - Gives up on chains if any line is too long? It might not be, because I can't see a specific "line" that's too long to format, but there's more detail about the exact problem in the issue.

Rustfmt is a tool that formats Rust code in compliance with style guidelines. Its name precisely reflects its purpose. To install rustfmt, you can run rustup component add rustfmt. Once installed, you can execute cargo fmt to format Rust code in your workspace. If you require further information, you can visit rustfmt’s GitHub repository.

code must be formatted with rustfmt.

Yes, some cases are not yet supported (https://github.com/rust-lang/rustfmt/issues/4914).

Just FYI, the let-else suggestions will only work until rustfmt settles on a format for it. So you may be surprised when this happens and it suddenly changes.