Go 1.22

Post by crowdyriver » Wed, Feb 07, 2024, 12:36 PM UTC

jhanschoo wrote: post #109

KingOfCoders wrote: post #38

Earlier quoted context omitted.

In my CTO newsletter I recently wrote about TS vs Go releases, with Go 1.22 as an example. TS gets more and more complicated with each release, catering to the power users. Go adds things that makes it simpler to use, like the (missing) range over integers. It's like game sequels, they add more and more canon and game mechanics, then game sequels (or comics) need to reset to make them more accessible to newcomers aga…

> TS gets more and more complicated with each release, catering to the power users. My understanding about the use of advanced/more expressive TR features is that it's OK if you don't use them, and don't bother wasting time for most products. Bot if you are writing a library of framework in TS, go ahead especially since they are meant to improve the experience of consumers.

Post by Zach_the_Lizard » Wed, Feb 07, 2024, 12:47 PM UTC

puika wrote: post #85

hambos22 wrote: post #64

Earlier quoted context omitted.

> can't wait for some map/filter/find slice functions though Till that day comes, you could use the "lo" library (inspired from lodash). It's my goto Swiss army knife for golang projects. https://github.com/samber/lo

On the other hand, I advise you NOT to use this kind of library and write simple, fast go code most of the time, with the occasional generics helper. Why the hell would I clutter my code with, for example: https://github.com/samber/lo?tab=readme-ov-file#fromentries-...

Post by simiones » Wed, Feb 07, 2024, 1:00 PM UTC

KingOfCoders wrote: post #98

simiones wrote: post #89

Earlier quoted context omitted.

All languages that keep evolving get more complex over time. The changes are always intended to make programs written in the language simpler. Go moves at a pretty slow pace, adding only minor new features (and thus minor complications) in most releases. Even in 1.22, they are previewing a new feature, range-over-functions, which seem to be basically C#/Python's iterator functions - a feature which will, of course, c…

"range-over-functions" Yes, something people coming to Go would have assumed worked before looking at all range cases, but didn't.

  s := []string{"hello", "world"}
  for i, x := range slices.Backward(s) {
    fmt.Println(i, x)
  }

  func Backward[E any](s []E) func(func(int, E) bool) {
    return func(yield func(int, E) bool) {
        for i := len(s)-1; i >= 0; i-- {
            if !yield(i, s[i]) {
                return
            }
        }
    }
  }

Post by KingOfCoders » Wed, Feb 07, 2024, 1:04 PM UTC

simiones wrote: post #115

KingOfCoders wrote: post #98

Earlier quoted context omitted.

"range-over-functions" Yes, something people coming to Go would have assumed worked before looking at all range cases, but didn't.

range-over-functions is the experimental new feature where a function can generate a sequence by executing a bit at a time, i.e. s := []string{"hello", "world"} for i, x := range slices.Backward(s) { fmt.Println(i, x) } func Backward[E any](s []E) func(func(int, E) bool) { return func(yield func(int, E) bool) { for i := len(s)-1; i >= 0; i-- { if !yield(i, s[i]) { return } } } } I don't think anyone expects this to w…

Post by mjw_byrne » Wed, Feb 07, 2024, 1:11 PM UTC