can I get branch coverage in text format?
--
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.
To view this discussion on the
what is the difference between go tool cover and go tool covdata ?
--
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.
To vi
On Wed, Jul 10, 2024 at 3:07 AM Akash Kumar wrote:
>
> what is the difference between go tool cover and go tool covdata ?
See https://pkg.go/dev/cmd/cover and https://pkg.go.dev/cmd/covdata.
Ian
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
Howdy,
I'm trying to establish a mental model for what the compiler does with
range functions in Go 1.23. It looks like the compiler creates a function
based on the for loop body, and calls it by looping over the values passed
in.
Meaning this code:
func simpleIter(yield func(v int) bool) {
On Wed, Jul 10, 2024 at 4:17 PM Justin Scheiber wrote:
>
> I'm trying to establish a mental model for what the compiler does with range
> functions in Go 1.23. It looks like the compiler creates a function based on
> the for loop body, and calls it by looping over the values passed in.
>
> Mean
I use this:
gitlab.com/fgmarand/gocoverstats
to do this:
gocoverstats -v -f coverage.txt -percent
Op woensdag 10 juli 2024 om 12:06:39 UTC+2 schreef Akash Kumar:
> can I get branch coverage in text format?
--
You received this message because you are subscribed to the Google Groups
"golang-nu
