cargo update & lint/clippy/rustfmt fixes.

Author: eddyb

.github/workflows/ci.yml

@@ -18,9 +18,8 @@ jobs:
           submodules: true
       - uses: actions-rs/toolchain@v1
         with:
-          # HACK(eddyb) only nightly supports setting `version = "Two"`
-          # in `rustfmt.toml`, which is needed to format array/slice patterns
-          # at all (see https://github.com/rust-lang/rustfmt/pull/4994).
+          # FIXME(eddyb) `style_edition = "2024"` in `rustfmt.toml` is what keeps
+          # this on `nightly`, should switch to `stable` when that stabilizes.
           toolchain: nightly
           override: true
 

Cargo.lock

@@ -34,6 +34,9 @@ serde = { version = "1.0", features = ["derive"] }
 serde_json = "1.0"
 smallvec = { version = "1.7.0", features = ["serde", "union"] }
 
+[lints.rust]
+unexpected_cfgs = { level = "warn", check-cfg = ['cfg(git_main_docs)'] }
+
 [package.metadata.docs.rs]
 all-features = true
 rustdoc-args = ["--cfg", "docsrs", "--document-private-items"]

Cargo.toml

@@ -1,6 +1,4 @@
-# HACK(eddyb) needed to format array/slice patterns at all, because it was a
-# breaking change (see https://github.com/rust-lang/rustfmt/pull/4994).
-version = "Two"
+style_edition = "2024"
 
 # HACK(eddyb) avoid random spilling of e.g. method call chains onto many lines.
 use_small_heuristics = "Max"

rustfmt.toml

@@ -104,7 +104,6 @@
     clippy::match_wild_err_arm,
     clippy::match_wildcard_for_single_variants,
     clippy::mem_forget,
-    clippy::mismatched_target_os,
     clippy::missing_enforced_import_renames,
     clippy::mut_mut,
     clippy::mutex_integer,
@@ -145,6 +144,9 @@
     // NOTE(eddyb) ignored because it's misguided to suggest `let mut s = ...;`
     // and `s.push_str(...);` when `+` is equivalent and does not require `let`.
     clippy::string_add,
+
+    // FIXME(eddyb) rework doc comments to conform to linted expectations.
+    clippy::too_long_first_doc_paragraph,
 )]
 // NOTE(eddyb) this is stronger than the "Embark standard lints" above, because
 // we almost never need `unsafe` code and this is a further "speed bump" to it.