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

core::trie needs an external iterator #5506

Closed
thestinger opened this issue Mar 22, 2013 · 1 comment
Closed

core::trie needs an external iterator #5506

thestinger opened this issue Mar 22, 2013 · 1 comment

Comments

@thestinger
Copy link
Contributor

This is needed to implement Set, and useful by itself too.

The each implementation just needs to be translated into a state machine, but it's not quite as simple as the std::treemap one - it needs to store a node, index and then a stack of nodes/indices up to the root.

@ghost ghost assigned thestinger Mar 22, 2013
@emberian
Copy link
Member

emberian commented Jul 7, 2013

Still relevant

@bors bors closed this as completed in d49bb43 Aug 5, 2013
@thestinger thestinger removed their assignment Jun 16, 2014
oli-obk pushed a commit to oli-obk/rust that referenced this issue May 2, 2020
Implement mismatched_target_os lint

I've extended the check suggested in the issue to all the currently supported operating systems instead of limiting it to `linux` and `macos`, let me know if we want to do this.

Also, I've restored the text `There are over XXX lints ...` in the README as it was matched against by `cargo dev new_lint`.

changelog: Added `mismatched_target_os` lint to warn when an operating system is used in target family position in a #[cfg] attribute

Closes rust-lang#3949
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 a pull request may close this issue.

2 participants