could this be a duplicate of #66626?

could this be a duplicate of #66626?

No, that issue relates to the go/types package, not reflect.

ah, overlooked this crucial detail, thank you!

This was in fact inspired by #66626, but yes, it is for reflect, not types.

Alternatively, the method value could be the iterator as opposed to returning an iterator, like so:

package reflect

type Type interface {
	...
	// Fields is a go1.23 iterator over all the fields of a struct type (etc).
	//
	// Example: for ftype := range t.Fields { ... }
	Fields(yield func(ftype *Func) bool)
}

func (t *rtype) Fields(yield func(ftype *Func) bool) {
	for i := range t.NumFields() {
		if !yield(t.Field(i)) {
			break
		}
	}
}

// client code
var t reflect.Type = ...
for ftype := range t.Fields { ... }

Maybe. That keeps from introducing an import dependency we might not want, but it goes against the general conventions used elsewhere.