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
Currently, RLS is high priority for me, but since the RLS links rustfmt directly, this is orthogonal to 1.0. So file-lines and anything about IDE integration is not a 1.0 blocker.
Anything with non-default options (i.e., non-rfc style).
Any non-standard workflow. The important use cases for 1.0 are:
rustfmt or cargo fmt on a whole project or a sub-module of it
run rustfmt on CI in some mode which indicates whether a project 'passes' formatting
cc rust-dev-tools/dev-tools-team#17
This is all WIP
All 1.0 issues note that a few of those are basically different angles on the same thing, so the actual list of things to do is shorter.
Infrastructure stuff
Bugs
blocking bugs
Things that could have bad consequences for 'common path' users (e.g., removing code in common cases).
Formatting issues
blocking formatting issues We also need to double check that we are adhering to the spec/RFC
Feature work
Non-goals
Currently, RLS is high priority for me, but since the RLS links rustfmt directly, this is orthogonal to 1.0. So file-lines and anything about IDE integration is not a 1.0 blocker.
Anything with non-default options (i.e., non-rfc style).
Any non-standard workflow. The important use cases for 1.0 are:
rustfmt
orcargo fmt
on a whole project or a sub-module of itAnything in #2109
Perfect formatting - it's software, there will always be bugs :-(
The text was updated successfully, but these errors were encountered: