go-oidc-middleware VS go-patterns

You can see the PR here and I attached the logs for the workflow run that did the comparison between the versions: https://github.com/XenitAB/go-oidc-middleware/pull/158

I’ve built a library to try and make it easier to consume these services and their JWTs that works with net/http, mux, chi, gin, echo and fiber if you don’t want to implement the logic of discovery and validation yourself: https://github.com/XenitAB/go-oidc-middleware

Source: https://github.com/XenitAB/go-oidc-middleware/blob/main/internal/oidc/cty.go

You can find the module here: https://github.com/XenitAB/go-oidc-middleware

I’ve been spending some free time building a http middleware to make it easy to validate JWT tokens from OpenID Providers: go-oidc-middleware

3). GO Patterns

Re Go, there are a lot of lot of good patterns available available, but a lot of them aren’t OOP specific. In fact, both Go and Rust have been influenced by multiple paradigms, including OOP. Like the FAQ says,

What's great is there are really great patterns to follow out there on github (both code patterns https://github.com/tmrts/go-patterns and examples https://github.com/avelino/awesome-go https://github.com/go-kit/kit and for the app itself, https://github.com/golang-standards/project-layout )... and for me a really naggy mentor who insists everything be "idiomatic go"

So I am trying to write a simple generator based on this pattern and the results are a little counter-intuitive. My goal is to create a generator like the above that takes a net.IPNet object and ranges over all net.IP`'s contained in that network. When printing results, I am seeing the same values show up in subsequent executions of the loop and am not sure why. Code follows: