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

librustc: Remove @ pointer patterns from the language #11305

Merged
merged 2 commits into from
Jan 14, 2014

Conversation

pcwalton
Copy link
Contributor

@pcwalton pcwalton commented Jan 4, 2014

@nikomatsakis
Copy link
Contributor

I see @cmr beat me to the punch -- I didn't read this super thoroughly, but I didn't see any obvious problems.

@bors bors closed this Jan 14, 2014
@bors bors merged commit 119c614 into rust-lang:master Jan 14, 2014
flip1995 pushed a commit to flip1995/rust that referenced this pull request Aug 11, 2023
[`redundant_guards`]: don't lint on float literals

Fixes rust-lang#11304

changelog: [`redundant_guards`]: don't lint on float literals

r? `@Centri3` i figured you are probably a good reviewer for this since you implemented the lint ^^
flip1995 pushed a commit to flip1995/rust that referenced this pull request Nov 28, 2024
rust-lang#13698)

Two changes to `redundant_guards`:

- Lint float literals. We used to do that before but that was changed in
rust-lang#11305 because at the time there was a future compat warning and it was
planned to make pattern matching floats a hard error.

In rust-lang#116284 it was decided to actually remove the lint and
only make matching `NAN` specifically a hard error. The `NAN` part isn't
relevant/important here because this PR only changes what literals are
warned and `f64::NAN` isn't a literal, but I've added a test anyway to
make sure we continue to not lint there.
- Don't lint CStr literals because that can't be a pattern right now
(fixes rust-lang#13681)

changelog: none
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