Initiate the inner usage of cfg_match (Library)

[c410-f3r]

cc #115585

Continuation of #116312

[rustbot]

r? @cuviper

(rustbot has picked a reviewer for you, use r? to override)

[rustbot]

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

[c410-f3r]

r? libs

[bors]

☔ The latest upstream changes (presumably #116407) made this pull request unmergeable. Please resolve the merge conflicts.

[c410-f3r]

r? libs

[rustbot]

Some changes occurred in src/tools/cargo

cc @ehuss

[bors]

⌛ Testing commit 131cc37 with merge 643f375...

[bors]

💔 Test failed - checks-actions

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

Submodule path 'src/doc/rust-by-example': checked out 'e188d5d466f7f3ff9f1d518393235f4fe951be46'
From https://github.com/rust-lang/rustc-dev-guide
 * branch            1f30cc7cca9a3433bc1872abdc98960b36c21ca0 -> FETCH_HEAD
Submodule path 'src/doc/rustc-dev-guide': checked out '1f30cc7cca9a3433bc1872abdc98960b36c21ca0'
##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
##[error]Process completed with exit code 143.

[c410-f3r]

Attempting with retry: sh -c git submodule deinit -f src/doc/nomicon src/tools/cargo src/doc/reference src/doc/book src/doc/rust-by-example library/stdarch src/doc/rustc-dev-guide src/doc/edition-guide src/llvm-project src/doc/embedded-book library/backtrace && git submodule sync && git submodule update -j 16 --init --recursive --depth 1 src/doc/nomicon src/tools/cargo src/doc/reference src/doc/book src/doc/rust-by-example library/stdarch src/doc/rustc-dev-guide src/doc/edition-guide src/llvm-project src/doc/embedded-book library/backtrace
error: could not lock config file .git/modules/library/backtrace/config: No such file or directory
warning: Could not unset core.worktree setting in submodule 'library/backtrace'
Cleared directory 'library/backtrace'
error: could not lock config file .git/modules/library/stdarch/config: No such file or directory
Cleared directory 'library/stdarch'
warning: Could not unset core.worktree setting in submodule 'library/stdarch'
error: could not lock config file .git/modules/src/doc/book/config: No such file or directory
warning: Could not unset core.worktree setting in submodule 'src/doc/book'
Cleared directory 'src/doc/book'
error: could not lock config file .git/modules/src/doc/edition-guide/config: No such file or directory
warning: Could not unset core.worktree setting in submodule 'src/doc/edition-guide'
Cleared directory 'src/doc/edition-guide'
error: could not lock config file .git/modules/src/doc/embedded-book/config: No such file or directory

Idk, looks unrelated

[Dylan-DPC]

@bors r=Mark-Simulacrum

[bors]

💡 This pull request was already approved, no need to approve it again.

• This pull request previously failed. You should add more commits to fix the bug, or use retry to trigger a build again.

[bors]

📌 Commit 131cc37 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[bors]

⌛ Testing commit 131cc37 with merge b95bc4b...

[rust-log-analyzer]

The job dist-x86_64-illumos failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[RUSTC-TIMING] object test:false 4.329
error: unused imports: `sigaddset`, `sigemptyset`
  --> library/std/src/sys/pal/unix/process/process_common.rs:82:24
   |
82 |         pub use libc::{sigemptyset, sigaddset};
   |
   = note: `-D unused-imports` implied by `-D warnings`
   = help: to override `-D warnings` add `#[allow(unused_imports)]`

[bors]

💔 Test failed - checks-actions

[bors]

☔ The latest upstream changes (presumably #121177) made this pull request unmergeable. Please resolve the merge conflicts.

[c410-f3r]

Sigh... Sorry @Mark-Simulacrum @Dylan-DPC, I don't have the energy or motivation to continue pursuing this PR.

EDIT: It became clear that the cfg prefix is a redundancy, as such, I will try to modify the syntax and these changes would make everything much more difficult.