/rust

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

Tracking issue for Iterator::copied #57127

Open
xfix opened this Issue Dec 26, 2018 · 2 comments

Comments

Assignees
No one assigned
Labels
B-unstable C-tracking-issue T-libs
Projects
None yet
Milestone
No milestone
4 participants
@xfix @SimonSapin @Centril @Dylan-DPC
@xfix
Copy link
Contributor

xfix commented Dec 26, 2018 •
edited

This is a tracking issue for Iterator::cloned.

Added in #56534. Feature gate: #![feature(iter_copied)].

Related feature: copied in #57126.

@xfix xfix referenced this issue Dec 26, 2018

Open

Tracking issue for Option::copied #57126

@Dylan-DPC Dylan-DPC added the C-tracking-issue label Dec 26, 2018

@Centril Centril added T-libs B-unstable labels Dec 28, 2018

@SimonSapin

This comment has been minimized.

Sign in to view
Copy link
Contributor

SimonSapin commented Feb 1, 2019

@Centril, do you feel your comment in #57126 (comment) is still an objection to the state of this feature, given the response in #57126 (comment)?
@Centril

This comment has been minimized.

Sign in to view
Copy link
Contributor

Centril commented Feb 1, 2019

@SimonSapin So ultimately, #57970 was closed meaning that we are comfortable with the specialization. If that specialization is always in place then Copied is a redundant type (and the impls that come with it are also redundant). However, keeping the cost and the Copied type also has less of a risk attached to it so there's a trade-off here. I don't know what the right choice is, but those are the facts as I see them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment