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

rename test::BenchHarness to test::Bencher #13030

Closed
wants to merge 1 commit into from

Conversation

liigo
Copy link
Contributor

@liigo liigo commented Mar 20, 2014

Closes #12640

@alexcrichton
Copy link
Member

Closing due to inactivity, but feel free to reopen with a rebase!

bors added a commit that referenced this pull request Apr 1, 2014
Closes #12640

based on PR #13030, rebased, and passed all tests.
bors added a commit that referenced this pull request Apr 11, 2014
Closes #12640

based on PR #13030, rebased, and passed all tests.
lnicola pushed a commit to lnicola/rust that referenced this pull request Aug 23, 2022
fix: escape keywords used as names in earlier editions

Fixes rust-lang#13030

There are keywords in Rust 2018+ that you can use as names without escaping when your crate is in Rust 2015 e.g. "try". We need to be consistent on how to keep track of the names regardless of how they are actually written in each crate. This patch attempts at it by taking such names into account and storing them uniformly in their escaped form.
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jul 11, 2024
Fix rust-lang#12964 - false positive with `into_iter_without_iter`

changelog: FP: `into_iter_without_iter`: No longer lints when the `iter` or `iter_mut` implementation is not within the first `impl` block

fixes rust-lang#12964

---

I'm pretty new to this open-source thing, so hopefully I did everything right. Got a little annoyed this false positive was happening in my code and the issue was inactive for two weeks so I thought I'd fix it myself.

As an aside, maybe `iter.map(...).next()` could be linted against? I don't see that ever being preferred over `iter.next().map(...)`, and it could've prevented the bug here.
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.

Rename test::BenchHarness to test::Bencher
3 participants