You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering, what is your position regarding the implementation of algorithms using generics on this repo?
Are you waiting a bit longer before upgrading to go 1.18, or should we do it now so that we can already start getting hands-on experience with generics?
I'm more than happy to bump the version now and I was thinking to start it but we need to do a bit of cleanup of the repository structure before we do that. Currently its all over the place 😓
I'll be opening a series of PR's to make these changes in an incremental (and traceable) way – will keep posting updates on this issue.
On the topic of constraints, I would like to use it but it's an experimental package and I would rather just create our own generic interfaces from ground up until we get some more data - that package was supposed to be just constraints instead of golang.org/x/exp/constraints but some members of the community didn't like this package for various reasons (mostly because of naming).
Hi everyone!
I was wondering, what is your position regarding the implementation of algorithms using generics on this repo?
Are you waiting a bit longer before upgrading to go 1.18, or should we do it now so that we can already start getting hands-on experience with generics?
If so, I recommend using the constraints defined in golang.org/x/exp/constraints as standard constraints!
The text was updated successfully, but these errors were encountered: