Skip to content

remove some oldmap::Hashmap from librustc #5201

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

Closed
wants to merge 1 commit into from

Conversation

yjh0502
Copy link
Contributor

@yjh0502 yjh0502 commented Mar 2, 2013

Switch some std::oldmap::HashMap to core::hashmap::linear::LinearMap.
related to #4986

@Thiez
Copy link
Contributor

Thiez commented Mar 3, 2013

I see a few instances of LinearMap(Something,()). Wouldn't it make more sense to replace those by LinearSet?

@yjh0502
Copy link
Contributor Author

yjh0502 commented Mar 4, 2013

@Thiez: I agree, but I encountered several weird bug while changing HashMap into LinearMap, or LinearMap<Something, ()> to LinearSet (for example, segmentation fault or illegal instruction exception). I don't know why it happens.

@yjh0502
Copy link
Contributor Author

yjh0502 commented Mar 5, 2013

I rebased the patch.

@graydon
Copy link
Contributor

graydon commented Mar 6, 2013

Unfortunately this requires another rebase.

@catamorphism
Copy link
Contributor

Sorry, I tried rebasing but way too many conflicts. I'm closing this; please open a new PR if you have time to rebase it, @yjh0502 . Thanks!

bors added a commit to rust-lang-ci/rust that referenced this pull request May 2, 2020
…sy-float-literal-restriction, r=flip1995

Move check for lossy whole-number floats out of `excessive_precision`

changelog: Add new lint `lossy_float_literal` to detect lossy whole number float literals and move it out of `excessive_precision` again.

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

4 participants