This is the tracking issue for core::iter::once_with().
Currently in nightly, PR = #57579.
Is this function now ready for stabilization?
I don鈥檛 see why not.
Tracked here:
pub fn once_with<A, F: FnOnce() -> A>(gen: F) -> OnceWith<F> {鈥
pub struct OnceWith<F> {鈥
impl<A, F: FnOnce() -> A> Iterator for OnceWith<F> {鈥
impl<A, F: FnOnce() -> A> DoubleEndedIterator for OnceWith<F> {鈥
impl<A, F: FnOnce() -> A> ExactSizeIterator for OnceWith<F> {鈥
impl<A, F: FnOnce() -> A> FusedIterator for OnceWith<F> {鈥
unsafe impl<A, F: FnOnce() -> A> TrustedLen for OnceWith<F> {鈥
@rfcbot fcp merge
Team member @SimonSapin 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.
:bell: This is now entering its final comment period, as per the review above. :bell:
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.
I noticed that this iterator has been stabilized a Copy impl which I assume wasn't intentional so I've submitted #68810 to remove it.
Most helpful comment
Is this function now ready for stabilization?