You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As noted in the contributing guide we use nightly ci tooling for rustfmt and rustdoc for a few features not available on stable. This issue lists the nightly features we use in the hope that one day we can just use stable for everything.
This is a developer workflow ergonomics issue, all our published crates work on stable.
The last two are ultimately less important if it came down to it. But, unfortunately, all of these have been unstable for ages. Our rustfmt.toml has not changed since it landed.
For now have opened an issue on rustfmt to allow us to at least bail if people accidentally use stable on rustfmt (which re-orders things badly): rust-lang/rustfmt#5022 . But that might also need to graduate (if the prs gets merged).
The text was updated successfully, but these errors were encountered:
As noted in the contributing guide we use nightly ci tooling for
rustfmt
andrustdoc
for a few features not available on stable. This issue lists the nightly features we use in the hope that one day we can just use stable for everything.This is a developer workflow ergonomics issue, all our published crates work on stable.
rustdoc
doc_cfg
forRUSTDOCFLAGS="--cfg docsrs"
rustfmt
In descending order of importance:
max_width
of our code1
to2
The last two are ultimately less important if it came down to it. But, unfortunately, all of these have been unstable for ages. Our rustfmt.toml has not changed since it landed.
For now have opened an issue on
rustfmt
to allow us to at least bail if people accidentally use stable on rustfmt (which re-orders things badly): rust-lang/rustfmt#5022 . But that might also need to graduate (if the prs gets merged).The text was updated successfully, but these errors were encountered: