-
Notifications
You must be signed in to change notification settings - Fork 297
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
cue/cmd: support generic Go types in cue get go
#2217
Comments
This feels somewhat urgent, even if we choose to treat generic types in a lazy way like "top", because generics are becoming increasingly common in Go code. And |
|
Latest for both (v0.5.0) - I just encountered the same issue. |
Will revisit when we plan/schedule the feature requests. |
I'm hitting this error when trying to |
reproducer, I see a change in errors for these k8s version, but changing go/cue version does not matter note, Go 1.21 will not work because
|
Interesting, if I change the
|
@verdverm thanks for the report. Just to summarise my understanding of the various issues at play (I couldn't get your repro to run for me). Given:
Use of
Use of
So the TL;DR from my perspective is:
Please let me know if there is anything that has fallen through the gaps in this analysis! |
Did you try |
Yes, per my comment above which gives the explanation as to why each fails:
But what I then failed to do was actually comment that your solution of |
Currently, use of generic structs results in a panic.
For example, this example:
results in the following testscript failure:
It would be better if it generated reasonable code similar to what's expected above instead.
r context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: