Skip to content

Investigate Cost of Making TrieMap and TreeMap's iterators DoubleEnded #17451

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
Closed
Gankra opened this issue Sep 22, 2014 · 2 comments
Closed

Investigate Cost of Making TrieMap and TreeMap's iterators DoubleEnded #17451

Gankra opened this issue Sep 22, 2014 · 2 comments

Comments

@Gankra
Copy link
Contributor

Gankra commented Sep 22, 2014

This will definitely pump up their implementation complexity, and probably their memory footprint a bit. Depends on the precise implementation. Still worth implementing to see. The proposed range() iterators would naturally fall out of such an implementation, though.
@Gankra
Copy link
Contributor Author

Gankra commented Sep 22, 2014

cc @aturon

@Gankra
Copy link
Contributor Author

Gankra commented Jan 6, 2015

TrieMap is not in std lib anymore.

@Gankra Gankra closed this as completed Jan 6, 2015
lnicola pushed a commit to lnicola/rust that referenced this issue Jul 11, 2024
@bors
Auto merge of rust-lang#17572 - beetrees:f16-f128, r=Veykril
8cc4de6 
Add `f16` and `f128` support

Adds `f16` and `f128` support, using the `rustc_apfloat` library (also used by `rustc`) for parsing/arithmetic/displaying since the types aren't stable yet so can't be used by rust-analyzer itself.

Issue: rust-lang#17451
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Gankra