go-linq

There are also libraries like https://github.com/Jeffail/tunny or https://pkg.go.dev/go.uber.org/goleak or https://github.com/fatih/semgroup to help deal with concurrency limits and goroutine lifecycle management. As the author of https://github.com/ahmetb/go-linq, it's hard to find adoption for libraries offering "syntactic sugar" in Go, as the language culture discourages those kind of abstractions and keeping the code straightforward.

This is a lot more possible now that Go has generics (as of 1.18). I would probably never use these, as I find such libraries are a whole new domain-specific language to learn, and often don't make things much simpler anyway, but here are some libraries where people have done something like this: - https://github.com/ahmetb/go-linq: modelled after LINQ, but created pre-generics so only recently added some generics features - https://github.com/samber/lo: kind of like JavaScript's lodash library but for Go 1.18+ (with generics) - https://github.com/asynkron/gofun: simple library with stand-alone functions to filter, map, and so on

FWIW not exactly related, but check out Go-LINQ as well. https://github.com/ahmetalpbalkan/go-linq (disclaimer: my project). I will take a look at combining RxGo and Go-LINQ and probably will write a blog post soon.

s

I have done something similar in the past: http://ahmetalpbalkan.github.io/go-linq/ (https://github.com/ahmetalpbalkan/go-linq) this also has filter/map functions (where/select in LINQ) I haven't used reflection but callers should make type assertions needed. This doesn't make things very slow but not very faster either. When you need performance, a code generator like this can help: http://clipperhouse.github.io/gen/