If you have Delve installed it allows you to execute step-by-step inside Go
library code.
Then you will know exactly what happens and will have access to the Windows
error code.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe fro
To give a little bit more background on what I was doing - I have an API
endpoint which is used to download large amounts of data that is backed by
S3 in AWS. Using an io.Pipe to simply proxy from S3 tops out at around
30MB/sec due to single threaded S3 performance and setup time. I wrote an
adapte
AFK but you might also like to post to
https://groups.google.com/forum/#!forum/golang-tools (per
https://github.com/golang/go/wiki/golang-tools)
On Sat, 23 Nov 2019, 15:46 T L, wrote:
> The packages.Config.ParseFileParseFile docs (
> https://godoc.org/golang.org/x/tools/go/packages#Config) says
The packages.Config.ParseFileParseFile docs
(https://godoc.org/golang.org/x/tools/go/packages#Config) says
// An application may supply a custom implementation of ParseFile
// to change the effective file contents or the behavior of the parser,
// or to modify the syntax tree. For exa
in regard of Sean comment and FTR,
Now using version go1.13.4
[clementauger@Host-001 ~] $ ll gow/
bin/ pkg/ src/
[clementauger@Host-001 ~] $ ll gow/
bin/ pkg/ src/
[clementauger@Host-001 ~] $ ll gow/pkg/mod/
cache/ github.com/ golang.org/ gopkg.in/
[clementauger@Host-001 ~] $ ll gow/pkg