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.

Sign up for GitHub

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

Jump to bottom

Remove the annihilate function from the crate map #8431

Closed
brson opened this issue Aug 10, 2013 · 0 comments
Closed

Remove the annihilate function from the crate map #8431

brson opened this issue Aug 10, 2013 · 0 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@brson
Copy link
Contributor

brson commented Aug 10, 2013

It's no longer needed.
@luqmana luqmana mentioned this issue Sep 24, 2013
Merged
bors added a commit that referenced this issue Sep 25, 2013
@bors
auto merge of #9470 : luqmana/rust/bba, r=brson
d7bb40c 
 #8431

~~@brson: do we need to bump up the cratemap version for this change?~~ Tis a no.
flip1995 pushed a commit to flip1995/rust that referenced this issue May 5, 2022
@bors
Auto merge of rust-lang#8431 - dswij:8416, r=xFrednet
d5c62fd 
`redundant_closure` fix FP on coerced closure

Closes rust-lang/rust-clippy#8416,
Closes rust-lang/rust-clippy#7812
Closes rust-lang/rust-clippy#8091

~~Seems like this is fixed in rust-lang#817 and regressed.~~

Ignore coerced closure false positives, but this will lead to some false negatives on resolvable generics. IMO, this is still an overall improvement

changelog: [`redundant_closure`] ignores coerced closure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brson