Maybe there is a language barrier. My statement implied Go was a modern language yet it did not have a streams package - not that it was not a modern language.
You seem to be looking for a fight and I’m not sure why. Why don’t you focus on solutions - it’s better for everyone. > On Aug 12, 2022, at 4:22 AM, Jan Mercl <0xj...@gmail.com> wrote: > > On Thu, Aug 11, 2022 at 11:18 PM Robert Engels <reng...@ix.netcom.com> wrote: > >> Every modern language with generics or similar has a streams package so >> there’s no need to call out Java. > > For some reason unknown to me you seem to consider Go not being a > modern language as it does not have a "streams" package. I don't care, > but it's worth noting. > > Back to the pipelining, error "models" and exceptions. Some languages > I consider not modern are limited to single values returned from a > function. That makes pipelining a problem if errors can get involved. > Exceptions are more or less a poor solution to overcome that > limitation. Go does not have this limitation so it does not need the > poor solution to it. Yet you call it a problem of the Go error > "model". It makes little sense to me. > > -- > 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/CAA40n-WRiskdC0NMb9R1A0H6Gs0hMN11XZyYhFjp8TxOF0i-Cw%40mail.gmail.com. -- 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/86720653-8822-4BFE-B296-E977F3D40524%40ix.netcom.com.
