Jacob Lifshay

Ok, I finished writing that program: https://github.com/programmerjake/find_iterators_without_default/tree/e77e64d9469d3915a3500699b002688f3fb8e9bb (edit: I added the full list of types without `Default` impls to the top comment) Here's the output for 1.92.0-nightly ([4645a7988](https://github.com/rust-lang/rust/commit/4645a7988) 2025-09-17): #...

yeah, after some point I kinda forgot the policy I wrote down and went more by which iterators I think being empty is a reasonable default (going off the `core::array::IntoIter`...

I'm planning on adjusting this ACP to propose that all iterators by convention should default to an empty iterator, unless the type comes with a strong expectation of the default...

I was assuming it'd just implement `Default` where `F: Default` -- that also seems like a good motivation for having more function items and capture-less lambdas implement `Default`

I don't think that's sound assuming you can convert `Pin` to `Pin` (which seems entirely reasonable) because `UniqueArc` lets you create `Weak`, so you can break the pinning guarantee: ```rust...