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

Implement N4009 - Uniform container erasure (erase_if) #62

Closed
gnzlbg opened this issue Oct 28, 2014 · 3 comments
Closed

Implement N4009 - Uniform container erasure (erase_if) #62

gnzlbg opened this issue Oct 28, 2014 · 3 comments

Comments

@gnzlbg
Copy link
Contributor

gnzlbg commented Oct 28, 2014

N4009 - Uniform container erasure defines erase_if which seems analogous to Boost.Range v2 erase_remove_if container algorithm.

@ericniebler
Copy link
Owner

I've recently started a broad investigation into container algorithms in general, per a recent discussion with @sean-parent. I think we've recently hit upon something. erase_if is certainly a likely candidate.

@gnzlbg
Copy link
Contributor Author

gnzlbg commented Oct 28, 2014

I've been completely stuck with work since two months already and that won't probably change in the foreseeable future.

I think that with erase_if your library would be a complete replacement of Boost.Range v2 already.

An interesting exercise could be to rewrite all Boost.Range v2 examples using range-v3 both as documentation and to see if something is missing.

@ericniebler
Copy link
Owner

Docs are a huge TODO, and porting the Boost.Range examples might be a good way to jump-start that effort, but I'm not worried about replacing Boost.Range in its entirety. erase_if is a container algorithm. Those are different beasts than range algorithms. Either we do container algorithms right as a class, or else it gets left out. I'm OK with that.

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

No branches or pull requests

2 participants