Proposal: xgo tool coverage merge -o cov.out cov-a.out cov-b.out about xgo HOT 6 CLOSED

@ccoVeille Yes it could be used as a standalone binary:

go install github.com/xhd2015/cmd/xgo/coverage@latest
coverage <cmd> [args]

Xgo packs it for convenience:

xgo tool coverage <cmd> [args]

from xgo.

This tool could be moved to his own repository, or could be documented as a binary that anyone could reuse no ?

from xgo.

@ccoVeille Yes it could be used as a standalone binary:

go install github.com/xhd2015/cmd/coverage@latest
coverage <cmd> [args]

Xgo packs it for convenience:

xgo tool coverage <cmd> [args]

coverage seems a bad name for a standalone binary

from xgo.

@ccoVeille Yes it could be used as a standalone binary:

go install github.com/xhd2015/cmd/coverage@latest
coverage <cmd> [args]

Xgo packs it for convenience:

xgo tool coverage <cmd> [args]

coverage seems a bad name for a standalone binary

Or could be renamed to these candidates:

• coverutil
• covutil
• covtool
• xgocov
• coverage-tool
• cover-tool
• cover-util
• xgo-coverage-tool
• xgo-cover-tool

Which do you think makes more sense?

from xgo.

I would say

• coverage-tool
• go-coverage-tool

I would tend to choose the second one, as it's go related.

My point of view about other suggestions

• util is not specific
• xgo shouldn't be used in the name as it's not dependent to xgo
• cover is for books, or comforter 😅

from xgo.

OK, seems fine, I'll rename the standalone tool name to go-coverage-tool later.

from xgo.