-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Labels
T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.
Milestone
Description
In:
- https://crater-reports.s3.amazonaws.com/beta-1.74-4/beta-2023-10-21/reg/maybe-dangling-0.1.0/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.74-4/beta-2023-10-21/reg/cfg-match-0.2.1/log.txt
[INFO] [stdout] error[E0658]: use of unstable library feature 'cfg_match'
[INFO] [stdout] --> src/maybe_dangling.rs:65:1
[INFO] [stdout] |
[INFO] [stdout] 65 | crate::cfg_match! {
[INFO] [stdout] | ^^^^^^^^^^^^^^^^
[INFO] [stdout] |
[INFO] [stdout] = note: see issue #115585 <https://github.com/rust-lang/rust/issues/115585> for more information
[INFO] [stdout]
[INFO] [stdout]
[INFO] [stdout] error: no rules expected the token `feature`
[INFO] [stdout] --> src/maybe_dangling.rs:66:5
[INFO] [stdout] |
[INFO] [stdout] 66 | feature = "nightly-dropck_eyepatch" => {
[INFO] [stdout] | ^^^^^^^ no rules expected this token in macro call
[INFO] [stdout] |
[INFO] [stdout] note: while trying to match `cfg`
[INFO] [stdout] --> /rustc/489647f984b2b3a5ee6b2a0d46a527c8d926ceae/library/core/src/macros/mod.rs:358:11
[INFO] [stdout]
[INFO] [stdout]
[INFO] [stdout] error[E0659]: `cfg_match` is ambiguous
[INFO] [stdout] --> src/lib.rs:42:5
[INFO] [stdout] |
[INFO] [stdout] 42 | use cfg_match;
[INFO] [stdout] | ^^^^^^^^^ ambiguous name
[INFO] [stdout] |
[INFO] [stdout] = note: ambiguous because of a conflict between a macro-expanded name and a less macro-expanded name from outer scope during import or macro resolution
[INFO] [stdout] = note: `cfg_match` could refer to a macro from prelude
Metadata
Metadata
Assignees
Labels
T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.