Tracking issue: 1.0

[nrc]

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

• Rustup distribution (see Stability tracking - Rustfmt rust-dev-tools/dev-tools-team#17)
• add 'unstable options' command line option (add 'unstable options' command line option #1975)
• audit command line options (Audit command line options #1976, Redesign CLI #1028)
• audit config options (Audit config options #1974)
• audit exit codes (Audit exit codes #1977)
• style guide RFC accepted (in FCP)
• Library API is stablised (Audit public API #2639)

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

• RFC style fully implemented
• performance is OK (Tracking issue: performance #338)
• skip attributes (Tracking issue: skip attributes #1978)

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 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

Anything in #2109

Perfect formatting - it's software, there will always be bugs :-(

[nrc]

Also need to check for issues on the impl period milestone that should get carried over to the 1.0 milestone

[nrc]

Formatting issues these are all potentially back compat issues and need to be fixed or triaged p-low before 1.0.

[nrc]

We're not quite in FCP, but there doesn't appear to be any blockers, closing.