https://stackoverflow.com/a/43918797/12211419
know of any others?
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/836756d6-0654-4341-8a2e-af57ff07a231%40googlegroups.com.
(then again, the fact that this works seems slightly concerning to me: https://play.golang.org/p/phWQ83wPQtx)
On Mon, Feb 10, 2020 at 4:15 AM 'Axel Wagner' via golang-nuts
<golan...@googlegroups.com> wrote:
>
> It's reflect, so I don't feel confident in making any absolute statements (we've talked about it a bunch; I just find the implications of that API far too unwieldy to handle), but I tend to agree. You need a reference value and Bytes() seems the only typed reference value you can get out of reflect.Value without using Interface() and type-assertion. I don't think this can be fixed either - not just because of compatibility, but also because it would impede fmt.Print*.
https://golang.org/issue/27727.