about summary refs log tree commit diff
path: root/compiler/rustc_span/src/source_map.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-10-17 02:48:03 +0000
committerbors <bors@rust-lang.org>2023-10-17 02:48:03 +0000
commitc07693c1608258f3577eb15057fc0744fa924ae9 (patch)
tree2e405a7c3f253f0439d12574971ca119ffe2d87a /compiler/rustc_span/src/source_map.rs
parent39164b84e0c6d94b15c78fcbf9bb5cfb76693045 (diff)
parent10ab51d69d8bd540f2704e343ece5e1184a385fb (diff)
downloadrust-c07693c1608258f3577eb15057fc0744fa924ae9.tar.gz
rust-c07693c1608258f3577eb15057fc0744fa924ae9.zip
Auto merge of #116477 - nnethercote:tidy-alpha-deps, r=wesleywiser
Use tidy to enforce alphabetical dependency ordering

I get annoyed when dependencies in `Cargo.toml` files are not in alphabetical order. The [style guide](https://github.com/rust-lang/rust/blob/master/src/doc/style-guide/src/cargo.md) agrees with me.

There are ongoing efforts to provide linting/formatting of `Cargo.toml` files, e.g. https://github.com/rust-lang/rustfmt/pull/5240, https://crates.io/crates/cargo-toml-lint, and https://github.com/TimonPost/cargo-toml-format. But it's far from clear what's the right approach.

So this PR does something very simple: it uses the order checking already present in tidy. This allows incremental application of ordering, starting right now, and avoiding the need for any kind of all-at-once conversion.

If we do end up using some more comprehensive `Cargo.toml` linting/formatting solution in the future, the `tidy-alphabetical` lines will be easy to remove.

r? `@wesleywiser`
Diffstat (limited to 'compiler/rustc_span/src/source_map.rs')
0 files changed, 0 insertions, 0 deletions