On Tue, Apr 12, 2016 at 12:32 AM, Maximo Cuadros wrote:
- None of the functionally on `cmd/go` [2] is exposed
Well, yes, it's a command, not a library, so it hasn't been written to
be extensible.

I'm not very familiar with how cmd/go works, but it's not obvious to
me what some of your improvements are. For example, you mention
"generating a unique `main.go` generated file, and compiling a unique
binary". How is this different from what "go test" does? Similarly,
you talk about nested tests. Do you mean the "..." in something like
"go test net/..."? Again, what's the difference in approach between
your PoC and cmd/go?

It may be that some of your observations are simply bugs in cmd/go,
and the best response could be the easier approach of patching cmd/go
instead of the harder approach of refactoring a library out of cmd/go.
Again, I'm not very familiar with cmd/go internals. If you provide
more specific proposals, or more details on what you said earlier,
perhaps somebody else with more knowledge could provide specific

You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts


Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 2 | next ›
Discussion Overview
groupgolang-dev @
postedApr 11, '16 at 5:22p
activeApr 14, '16 at 2:58a

2 users in discussion

Nigel Tao: 1 post Maximo Cuadros: 1 post



site design / logo © 2021 Grokbase