-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
*types.TypeParam mishandling when using pointer type #577
Comments
Thanks for reporting this bug with a reproducer! Looking into it. |
I was wrongly assumed that, if `used` has an `Elem` method, then `origin` must too. But it does not if it's a type parameter. Add a test case too, which panicked before the fix. Fixes burrowers#577.
I was wrongly assumed that, if `used` has an `Elem` method, then `origin` must too. But it does not if it's a type parameter. Add a test case too, which panicked before the fix. Fixes #577.
Howdy, is this going to be added in a release soon? (Sorry to ping a closed issue) Just planning to use this in my project and would like to be able to use @latest for the install command :) |
We will do a release soon, but given that there have just been two bug fixes so far and people can use master now, we're not in a terrible rush. See https://github.com/burrowers/garble/blob/master/CHANGELOG.md. |
Ah awesome! Not meaning to rush ya'll was just wondering about this (and being selfish with wanting to use it :P) |
What version of Garble and Go are you using?
What environment are you running Garble on?
go env
OutputWhat did you do?
It's a very specific, I would even say edge-case use of Garble. I've defined type with generic and underlying type being slice of the generic. I've created function which returns this type - the tricky part is that generic is a pointer type (it only errors with pointer, values work well).
Please take a look at my playground to ensure reproducibility
https://go.dev/play/p/wwNYKnXAiuv
What did you expect to see?
No error; Working program
What did you see instead?
The text was updated successfully, but these errors were encountered: