Re:Iterators are (maybe) coming to Go
by anonymoushn on Saturday August 12, 2023 @05:07AM
(#37098368)
This does not contain anything about the proposed implementation of Pull, of course.
Wouldn't this be the implementation?
func Pull[V any](push func(yield func(V) bool)) (pull func() (V, bool), stop func()) {
... // snipped because it's big
}
Re:Iterators are (maybe) coming to Go
by anonymoushn on Saturday August 12, 2023 @11:43PM
(#37106481)
That is an implementation in terms of primitives that are not in the proposal.
I don't believe so - the post is pretty much all about how you can do this right now in normal Go code. And e.g. a bit after that is a link to the "full code" which is runnable: https://go.dev/play/p/hniFxnbXTgH
Possibly you're interpreting yield as a new keyword? It's just an argument to Pull.
The only not-(currently-)available-in-Go stuff that I can recall from the post is the performance optimization at the very end.
Re:Iterators are (maybe) coming to Go
by anonymoushn on Sunday August 13, 2023 @12:44PM
(#37111578)
You can read the proposal here: https://github.com/golang/go/issues/61405. It is linked in the first paragraph of TFA.
Yes, I know you can build a 100x-too-slow version of this on top of channels, but that's not the proposed extension to the language.
I suspect getting a single item out will be that you just make a
func next[T](i iterfunc[T]) T {
var item T
i(func(it T) bool){
item = it
return true // likely
})
return item
}
and use it. Semantics should be the same as ranging would desugar to (since that's all this is), though the variable arity will be slightly annoying of course.
Re:Iterators are (maybe) coming to Go
by anonymoushn on Saturday August 12, 2023 @05:08AM
(#37098377)
Sure, and that should be somewhere in the very long posts about this or in the very long github issue.
Re:Iterators are (maybe) coming to Go
by assbuttbuttass on Saturday August 12, 2023 @10:14AM
(#37100412)
I don't think it's so easy. An iterfunc doesn't store any state explicitly, so each time you call i it restarts from the beginning
Aah, yes, that's an excellent point. Thanks! That does complicate things a lot more.
Quite a lot more, as it essentially means you can only consume from iterators you create... which sorta defeats the purpose of iterators as a value, and degrades them almost completely to just a `range` helper.
As is the proposal says "there should be some coro.Pull type thing" which is a bit terse and says nothing about whether the implementation of coro.Pull will be fast or whether it will be built on range + channels