Tracking issue for DoubleEndedIterator::rfold (feature `iter_rfold`)

[bluss]

This is a tracking issue for DoubleEndedIterator::rfold (feature iter_rfold)

• Implemented in PR Add iterator method .rfold(init, function); the reverse of fold #44682
• rustdoc: DoubleEndedIterator::rfold
• related issue about rfind is Tracking issue for (DoubleEnded)?Iterator::rfind #39480

[bluss]

More rfold impls in #44856

[scottmcm]

Is this ready for a stabilization PR? I don't think there are any open questions...

[bluss]

I'd love to see this stabilized too.

The trait question where to place it (same as rfind) is the only one. I'm interested in what others think about that.

[SimonSapin]

Looks good to me to stabilize.

@rfcbot fcp merge

[rfcbot]

Team member @SimonSapin has proposed to merge this. The next step is review by the rest of the tagged teams:

• @Kimundi
• @SimonSapin
• @alexcrichton
• @aturon
• @dtolnay
• @sfackler
• @withoutboats

No concerns currently listed.

Once a majority of reviewers approve (and none object), 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.

[withoutboats]

I'm glad this was implemented on DoubleEndedIterator. The more niche methods are added to Iterator, the harder it is for users (especially new users) to find the non-niche method they're looking for. Since this method is extremely niche (an optimization of a very uncommon operation - folding in reverse), I think it would be "method bloat" to add it to Iterator.

I'm just noting this because I was going to register a concern about adding this to Iterator until I saw that it was added to DoubleEndedIterator instead.

[rfcbot]

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