Skip to content

Tracking issue for rustfmt #788

@tcharding

Description

@tcharding

Please not: There is not strong consensus that we should enable rustfmt

This is a tracking issue for pursuing the idea and helping reach consensus.

Previous discussion on rustfmt:

The main blockers to getting consensus

  1. Showing that the results of rustfmt'd code are acceptable to folks [1]
  2. Working out how to manage the massive changes in a safe reviewable manner

This is likely an organization wide change because it will painful for devs to have to configure their environment differently for different repos in the org?

[1] implies agreeing on a configuration of rustfmt that is acceptable to folks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions