Go 1.23: Custom Iterators Explained - Best feature?!

[@RaminRowshan]

Thank you for your video! It would be very helpful if you could also share your code by providing a link in the video description.

[@siya.abc123]

Congratulations on 10K subs sir. I'm happy I was here before this milestone 😊

[@FloWoelki]

Thank you very much! I appreciate that you are part of this journey!

[@bopon4090]

Its confusing af. All the callback and syntactic sugar kind of hard to understand

[@epsi]

Try coding similar behavior yourself without the syntactic sugar and the runtime hack that allows you to use range func(yield func[V any](V) bool) range func(yield func[K, V any](K, V) bool) Once you demystify the yield function and how it works with the loop, it starts to make more sense. That said, i agree with you. It's definitely not intuitive, and i get the feeling it's going to be one of the ugliest parts of Go until something better comes along. Channels are one of the easiest things to use and understand despite their inherent complexity, so to see something like this make it into the language as a standard feature is quite sad.

[@y.m.o6171]

pray tell how you are making these videos they are awesome !

[@LielAlmog]

Do you think people will start creating their own iterators for utilities (like iterate over a slice in reversed order) or we’ll see more packages like in JS, where there are many packages that give built in functionalities

[@FloWoelki]

Honestly, I do think that some people will create their own iterators for their libraries because they give you a lot of flexibility and developer-friendliness. Clearly, I cannot predict the future, so let's see where it goes :D

[@selvamp5775]

Function inside function inside another function... Little confused, hope will get it know.

[@fntr]

what code editor do you use atm and in this vid?

[@FloWoelki]

I use the Zed Editor :)

[@rahman9418]

Are you interested in creating a Udemy course? to teach the go language, because you explained it very well with an interactive video

[@themannyzaur]

thank God I'm not the only one confused

[@flipflap4673]

Not sure where I read that Golang is a fool proof language, easy to learn for any noob.

[@gungun974]

@@epsigo never really changed, again if you don’t like a feature, just don’t use it. The day when Golang will become craps, it’s will be the day of the 2.0 update where old codes will just broke. Until them, there are nothing to worry.

[@eddymoreno3818]

the sintaxis is ugly , i prefered it if it was a interface with a HasNext and Next methods or something like that

[@FloWoelki]

Yeah, the syntax is just mental :D Something like custom iterators in Rust is way more beautiful than in Go. But yeah, there were also a lot of discussions in the community; let's see where it goes.

[@flarebear5346]

The syntax is the way it is because of performance issues when using interfaces. This syntax allows you to use the functionality completely in the stack without needing to access the heap

[@FloWoelki]

@@flarebear5346 Also, I think it might be against the idiomatic practices of Golang. So, Go emphasizes simplicity and directness, avoiding more complex design patterns. But all in all, you will probably most likely won't use iterators that much :D

[@sm5172]

It's like a dog scratching his right ear with his left leg. Terrible syntactic choices, in my opinion.

[@pookiepats]

Again, fix the Go Gopher art or this entire playlist is copyright infringement

[@FloWoelki]

Thank you for the information. Would a short notice in the KZbin description be enough, or what do you recommend?