Hi Jeremy, I really appreciate all the materials you have shared.
I could understand that wrapping errors with informative messages is one of
important best practice treating errors. I'll keep it mind that :)
It was also very helpful to read errors section in Effective Go which you
Hi Mike, thank you so much for sharing your thoughts and all those
resources with concrete examples. Those really help me to understand how
errors in go work and how it is different from errors in Java.
Based on what you've shared, here's how I understand it:
In essence, because an e
some best practices that API providers can follow to help API users handle
errors effectively?
--
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 g
I'm so glad to hear it helped you!
> I wonder where the blog author found that flag? It's not exposed in `go
test`
I guess "-test.gocoverdir" parameter is not exposed to go test users well.
There is an another comment that it was very hard to find documents about
"
Have you try go test with -args -test.gocoverdir parameters?
> go test -cover ./... -args -test.gocoverdir="{a directory where coverage
reports should be generated}"
I found this blog post is very helpful when merging unit and integration
test coverage reports.
https://dustinspec
std
>>>> ... would output a valid JSON document, because
>>>> go help list
>>>> writes:
>>>> The -json flag causes the package data to be printed in JSON format
>>>> instead of using the template format.
>>>> but ...
>>
everal files .go and polymer (.html)? Thanks, Karl
>
--
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+unsubscr...@googlegroups.com.
For
