You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goquery package itself has already implemented the Iter interface. Have you considered supporting the 1.23 iterator, allowing users to directly use for-range on it?
goquery has already implemented its own Iter. Directly switching to iter.Seq or iter.Seq2 in version 1.23 is not practical. Therefore, my idea is to implement an adapter to convert it to iter.Seq or iter.Seq2.
Yes, this is on my todo list and I have a patch locally. I will gradually update the Go version carefully, while watching the reactions to the new features. Please wait.
Hi @itchyny,
The goquery package itself has already implemented the
Iter
interface. Have you considered supporting the 1.23 iterator, allowing users to directly usefor-range
on it?goquery has already implemented its own
Iter
. Directly switching toiter.Seq
oriter.Seq2
in version 1.23 is not practical. Therefore, my idea is to implement an adapter to convert it toiter.Seq
oriter.Seq2
.Here is my rough idea.
The client will use it like this. Here is the code from the readme example, modified to use
ToSeq2
:The text was updated successfully, but these errors were encountered: