I see. I was thinking of it from the point of view of the author of this yield/consume function. From that party's perspective, this function expresses the consumption of the value, not its production. But since the new go lang feature will make that not an explicit function, that is not the most germane point of view.
(Yes, I know what Marvin mentioned.) Thanks, Mike On Wednesday, February 7, 2024 at 1:18:00 PM UTC-5 Marvin Renich wrote: > * mspre...@gmail.com <mspre...@gmail.com> [240207 10:43]: > > The go language is getting better and better for functional programming, > > and I am here for it. I have enjoyed using APL, Scheme, Python. I was > > excited to see https://go.dev/wiki/RangefuncExperiment . However, I am > > puzzled by the choice to name the function parameter that _receives_ a > > Seq's values "yield". That func does the _complement_ to "yield", it > > _receives_ the value. Compare with Python's "yield" statement, which > > _provides_ the value. Couldn't we call the func parameter that receives > a > > Seq's values something like "receive" or "consume"? > > In addition to what Axel said, note that "yield" is just an arbitrary > function argument name; you may name it anything you choose. Try > changing "yield" to "abc" and it will still work. > > ...Marvin > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/59e03cd0-9562-4359-ae28-d54bda412bbcn%40googlegroups.com.
