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 fail_unless! #5628

Merged
merged 1 commit into from
Mar 30, 2013
Merged

librustc: Remove fail_unless! #5628

merged 1 commit into from
Mar 30, 2013

Conversation

brson
Copy link
Contributor

@brson brson commented Mar 29, 2013

No description provided.

bors added a commit that referenced this pull request Mar 29, 2013
@bors bors closed this Mar 30, 2013
@bors bors merged commit 1e91595 into rust-lang:incoming Mar 30, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request May 27, 2020
…eversed_empty_ranges, r=phansch

reversed_empty_ranges: add suggestion for &slice[N..N]

As discussed in the issue thread, the user accepted this solution. Let me know if this is what we want, or if changing the way we lint the N..N case is prefered.

changelog: reversed_empty_ranges: add suggestion for &slice[N..N]

Closes rust-lang#5628
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jan 12, 2023
…or` loop.

Reading the documentation for the lint, one could expect that the lint works in all cases that `X == Y`. This is false.

While the lint was updated, the documentation wasn't.

More information about the `N..N` problem in rust-lang#5689 and rust-lang#5628
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jan 12, 2023
…dswij

[rust-lang#10167] Clarify that the lint only works if x eq. y in a `for` loop.

Reading the documentation for the lint, one could expect that the lint works in all cases that `X == Y`. This is false.

While the lint was updated, the documentation wasn't.

More information about the `N..N` problem in rust-lang#5689 and rust-lang#5628

---

Fixes rust-lang#10167
changelog: [`reversed_empty_ranges`]: Update and clarify documentation
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