On Tuesday, July 12, 2016 at 11:26:57 PM UTC-6, Ian Lance Taylor wrote:
>
> On Tue, Jul 12, 2016 at 9:36 PM, Zac Pullar-Strecker > wrote:
> > Commands like go run, go build and go test amoung others should have
> > coloured output when an error occurs. it would make reading stack traces
> a
github.com/maruel/panicparse is a good package to do this if you need
it.
On Tue, 2016-07-12 at 22:26 -0700, Ian Lance Taylor wrote:
> On Tue, Jul 12, 2016 at 9:36 PM, Zac Pullar-Strecker wrote:
> > Commands like go run, go build and go test amoung others should have
> > coloured output when an e
On Tue, Jul 12, 2016 at 9:36 PM, Zac Pullar-Strecker wrote:
> Commands like go run, go build and go test amoung others should have
> coloured output when an error occurs. it would make reading stack traces a
> lot easier. I personally use the go run tool a lot during development
> because I have n
Commands like go run, go build and go test amoung others should have
coloured output when an error occurs. it would make reading stack traces a
lot easier. I personally use the go run tool a lot during development
because I have no reason to keep a binary in the $GOPATH/bin directory when
it's
