That's not a mistake. It's still a bug! Just doesn't seem like a very
severe one. I filed https://github.com/golang/go/issues/21631.
On Fri, Aug 25, 2017 at 3:08 PM, lukas.malkmus via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> I'm sorry, I think I made a huge mistake. The malicious
I'm sorry, I think I made a huge mistake. The malicious output only occurs
when running go test with the -race flag.
Am Freitag, 25. August 2017 22:35:21 UTC+2 schrieb lukas@googlemail.com:
>
> I'm using helper functions in my test, for example this one:
>
> // assert fails the test if the
Yeah, sorry, I misread the report.
I can't reproduce the issue. Can you give a complete runnable example.
On Fri, Aug 25, 2017 at 1:46 PM, lukas.malkmus via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> It is part of the interface...
>
>
> Am Freitag, 25. August 2017 22:35:21 UTC+2
It is part of the interface...
Am Freitag, 25. August 2017 22:35:21 UTC+2 schrieb lukas@googlemail.com:
>
> I'm using helper functions in my test, for example this one:
>
> // assert fails the test if the condition is false.
> func assert(tb testing.TB, condition bool, msg string, v
