The fmt job runs on stable, and stable rustfmt does not fail on a nightly-only option: it prints "unstable features are only available in nightly channel" and carries on with its own defaults. Carrying ten of them in the config is what let the tree drift from what the job expects. This corrects the previous commit, which claimed all ten were ignored. Nine are. `version = "Two"` is not: despite the warning saying it cannot be set, on stable it still drives import order and collapses short if/else onto one line. Dropping it reformats 18 files back to the default style, which is the bulk of this diff. Dropped anyway, so the repository's style stops depending on behavior the tool itself says it does not support and could stop honoring in any release. The file now records that, so the options do not come back without the fmt job moving to nightly along with them. Verified: cargo fmt --all -- --check exits 0 with no warnings and no diffs, 138 unit tests pass, clippy --all-targets -- -D warnings stays at zero.
17 lines
901 B
TOML
17 lines
901 B
TOML
# So opcao estavel aqui, de proposito. O CI roda `cargo fmt --all -- --check` em
|
|
# stable, e no stable a opcao de nightly nao falha: o rustfmt avisa "unstable
|
|
# features are only available in nightly channel" e segue em frente. Este arquivo
|
|
# pedia dez delas, entao a arvore formatada em nightly nunca batia com o que o
|
|
# job esperava, e ele vivia vermelho.
|
|
#
|
|
# Cuidado com o `version = "Two"`: o aviso diz que nao da para setar, mas ele
|
|
# MUDA a saida no stable (ordem dos imports e if/else curto numa linha). Foi
|
|
# removido assim mesmo, para o estilo do repositorio nao depender de um
|
|
# comportamento que a propria ferramenta diz nao suportar e que pode sumir numa
|
|
# versao qualquer. Se alguma dessas opcoes voltar, o job de fmt do CI tem que ir
|
|
# para nightly junto, senao a divergencia volta com ela.
|
|
max_width = 160
|
|
newline_style = "Unix"
|
|
use_field_init_shorthand = true
|
|
use_try_shorthand = true
|