Thanks. Tools are fine, but a new developer has to know about them. So I
think it would still be super useful if golang.org documentation had this
information already generated. In bytes.Reader I should be able to see
'Implements ReadSeeker etc', and in ReadSeeker I should be able to see
'Imp
bytes.Reader is what I was looking for, thanks all!
Seems like if it this information can be generated, then it should probably
be included in the main documentation? I don't know how anyone new to the
language would ever work that out otherwise.
I have vscode 1.33, which support guru (using
I have another strange interface with the Go AWS SDK. The PutObject is
expecting the data as an: io.ReadSeeker
I imagine there is something implementing this in Go. But my question is
how would a new user find this information? The go documentation for the
API just tells me there is a Reader
Thanks, that's working just as I needed. I have 4 build targets from a
single pkg+ sub pkgs, so this lets me now see what's going on, and also
keep an audit of what was built.
It's a shame vscode can't flag the files, I'm having to use file names with
the tags to find my way around, but at l
Thanks Ian.
I should have mentioned that I am using go 1.12.1 with modules.
So my 'main' package/module has a number of sub-folder packages as
dependencies. I found the -deps option, but that seems to include every
dependency (also useful info) but is there a way to limit that to just my
so
My project is growing and I have started using custom build tags. When I
build the project I would really like to see a list of all the files that
have been selected based on the tags I have requested. Is that possible?
Thanks, Peter
--
You received this message because you are subscribed t
