many of my colleges are working on Windows, they fail to run `go test`
commands due to syscalls: our projects are heavily using syscalls, their
existences make it impossible to compile on Windows, which lead to this
situation where most of my colleges simple can't run any test code even
it's as simple as this:
```
func Test_FOO(t *testing.T){
fmt.Print("foo")
}
```
This simple piece of code doesn't use syscall but fails to compile anyway.
Is there any chance that `go test` being able to just compile whatever it
needs rather than the whole project including the part that contains
syscalls?
--
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 web visit
https://groups.google.com/d/msgid/golang-nuts/1b6ab3df-3ec0-42ef-92c7-00d66ccdc75en%40googlegroups.com.
