Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move fourcc to HOST_CRATES #12159

Merged
merged 1 commit into from
Feb 11, 2014
Merged

Move fourcc to HOST_CRATES #12159

merged 1 commit into from
Feb 11, 2014

Conversation

alexcrichton
Copy link
Member

It depends on libsyntax, which is a host crate, so it can't be in the target
crates section.

It depends on libsyntax, which is a host crate, so it can't be in the target
crates section.
bors added a commit that referenced this pull request Feb 11, 2014
It depends on libsyntax, which is a host crate, so it can't be in the target
crates section.
@bors bors closed this Feb 11, 2014
@bors bors merged commit e257011 into rust-lang:master Feb 11, 2014
@alexcrichton alexcrichton deleted the move-fourcc branch February 14, 2014 04:22
bors added a commit to rust-lang-ci/rust that referenced this pull request Jul 25, 2022
internal: Lift out macro bang property from completion PathKind enum
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jan 25, 2024
[`default_numeric_fallback`]: improve const context detection

Fixes rust-lang#12159

The lint didn't actually recognize any of the associated consts (in the linked issue), because in those cases the parent is an `ImplItem` and not an `Item`, but it only actually emitted a lint for i32 and f64 because the other cases failed the very last check here
https://github.com/rust-lang/rust-clippy/blob/bb2d4973648b1af18d7ba6a3028ed7c92fde07fb/clippy_lints/src/default_numeric_fallback.rs#L91-L96

A better check for detecting constness would be using `body_const_context`, which is what this PR does.

changelog: [`default_numeric_fallback`]: recognize associated consts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants