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

Fix compiletest on windows #5704

Merged
merged 1 commit into from
Apr 4, 2013
Merged

Fix compiletest on windows #5704

merged 1 commit into from
Apr 4, 2013

Conversation

brson
Copy link
Contributor

@brson brson commented Apr 3, 2013

No description provided.

bors added a commit that referenced this pull request Apr 4, 2013
@bors bors closed this Apr 4, 2013
@bors bors merged commit 34b2336 into rust-lang:incoming Apr 4, 2013
flip1995 added a commit to flip1995/rust that referenced this pull request Jun 23, 2020
Downgrade unnested_or_patterns to pedantic

Even with rust-lang#5704 fixed, I don't believe it is a safe bet that if someone is using or-patterns anywhere in a codebase then they want to use it as much as possible in the whole codebase. I think it would be reasonable to reevaluate after the feature is stable. I feel that a warn-by-default lint suggesting use of an unstable feature, even if already being used in one place, is questionable.

changelog: Remove unnested_or_patterns from default set of enabled lints
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jul 14, 2020
Require `or_patterns` to suggest nesting them

changelog: Require `#![feature(or_patterns)]` to trigger [`unnested_or_patterns`]

Fixes rust-lang#5704
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