Docs suggest implemting try_fold on std::iter::iterator, which is not possible due to Try being unstable

[mpdn]

std::iter::Iterator docs has this "Note to implementors" on try_fold:

Most of the other (forward) methods have default implementations in terms of this one, so try to implement this explicitly if it can do something better than the default for loop implementation.

But this isn't actually possible to do in stable due to the Try trait being unsable. The type bounds cannot be specified correctly to match the iterator definition.

[hkBst]

Implementors can use the unstable Try trait, or directly implement the methods they care about optimizing. It is perhaps unfortunate that Try is not stable, but that is not something that can be fixed with docs. I'm not sure what your expectation is here.

[lolbinarycat]

The documentation could at least mention the instability of Try.