Skip to content

Tracking issue for ops::Bound::cloned() #61356

@czipperz

Description

@czipperz
Contributor

This is needed because RangeBounds::start_bound() returns Bound(&T) but I need a Bound(T).

Activity

added
C-feature-requestCategory: A feature request, i.e: not implemented / a PR.
T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.
on May 30, 2019
added a commit that references this issue on Jun 6, 2019
6c5c143
added a commit that references this issue on Jun 6, 2019
654854f
changed the title [-]Add `.cloned()` method to `ops::Bound`.[/-] [+]Tracking issue: Add `.cloned()` method to `ops::Bound`.[/+] on Jul 7, 2019
czipperz

czipperz commented on Jul 7, 2019

@czipperz
Author
changed the title [-]Tracking issue: Add `.cloned()` method to `ops::Bound`.[/-] [+]Tracking issue for `ops::Bound::cloned()`[/+] on Jul 7, 2019
added
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
B-unstableBlocker: Implemented in the nightly compiler and unstable.
and removed
C-feature-requestCategory: A feature request, i.e: not implemented / a PR.
on Jul 7, 2019
added
Libs-TrackedLibs issues that are tracked on the team's project board.
on Jul 30, 2020

2 remaining items

rfcbot

rfcbot commented on Jun 8, 2021

@rfcbot
Collaborator

Team member @m-ou-se has proposed to merge this. The next step is review by the rest of the tagged team members:

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

added
proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.
final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
and removed
proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
on Jun 8, 2021
rfcbot

rfcbot commented on Jun 14, 2021

@rfcbot
Collaborator

🔔 This is now entering its final comment period, as per the review above. 🔔

added and removed
final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
on Jun 24, 2021
rfcbot

rfcbot commented on Jun 24, 2021

@rfcbot
Collaborator

The final comment period, with a disposition to merge, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

The RFC will be merged soon.

added a commit that references this issue on Jul 2, 2021
cd3a48f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

B-unstableBlocker: Implemented in the nightly compiler and unstable.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCLibs-TrackedLibs issues that are tracked on the team's project board.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    Participants

    @vorot93@m-ou-se@Centril@jonas-schievink@apiraino

    Issue actions

      Tracking issue for `ops::Bound::cloned()` · Issue #61356 · rust-lang/rust