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

[ranges] Range adaptor/factory objects not indexed #3232

Closed
morinmorin opened this issue Sep 17, 2019 · 6 comments · Fixed by #3280
Closed

[ranges] Range adaptor/factory objects not indexed #3232

morinmorin opened this issue Sep 17, 2019 · 6 comments · Fixed by #3280
Assignees

Comments

@morinmorin
Copy link
Contributor

Range adaptor objects (filter, transform, ...) and factory objects (iota, ...) are not indexed.

@jensmaurer jensmaurer changed the title Range adaptor/factory objects not indexed [ranges] Range adaptor/factory objects not indexed Sep 24, 2019
@jensmaurer
Copy link
Member

Let's wait for #3233 to land.

@jensmaurer
Copy link
Member

#3233 has landed.

@morinmorin
Copy link
Contributor Author

It looks like #3280 adds index entries for range adaptors (filter_view, transform_view, …) but not for range adaptor objects (filter, transform, …) or range factory objects (iota, …).

BTW, do we add index entries for keys_view and values_view from [ranges.sys]? (While they also appear at [range.elements.overview], keys and values would only appear at [ranges.sys].)

@morinmorin
Copy link
Contributor Author

@jensmaurer, if you could guide me what macro to use for indexing range adaptor objects (and range factory objects), I'll make a PR.

Thanks.

@jensmaurer
Copy link
Member

I'd really like to fix this while addressing #3134, otherwise there will be a lot of editing conflicts.

@morinmorin
Copy link
Contributor Author

Sure, no hurry :)
I missed that issue. Thanks for pointing it out.

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