-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v4: Golang 1.18 Generics #309
Comments
Probably none. Generics can help replace some of the code duplication, such as the |
If you can write a prototype of a |
1.18 should be coming out this month, but I understand if you want it to soak for a bit. Also I was thinking adding generics support would be enough to warrant going to v4 as it changes the way you interact with the interface quite a bit. |
This issue turned out to be more complicated than I thought. I expected |
After reading the code quite a bit, reflection is used all over. It seems like with golang 1.18 coming out with generics, quite a bit of this could be replaced with generics. What areas would be best to replace reflection with generics?
The text was updated successfully, but these errors were encountered: