4 ms·
Thanks for your feedback. We realize that Go's aim for simplicity is paramount in the design of the language, and wanted to respect that by making the DSL clean
by mholt 13y ago
Thanks for your feedback. We realize that Go's aim for simplicity is paramount in the design of the language, and wanted to respect that by making the DSL clean as it is. Without worrying what's under the hood, it feels Go-esque, and resolves a few problems.
For instance, with native Go tests, your `if` statements have inverted logic: if a != b, then it's an error, instead of, a should equal b. Further, inferring clear intent from just "TestThisOrThat" as documentation is nearly impossible.
Fortunately, Go doesn't compile testing packages or files into the final binaries, and the testing framework only has to exist once in your Go workspace, so Go still keeps things pretty tidy.
(For the record, I was insistent on using Go's built-in stuff until I realized that the Go engineers were humans too, and the language isn't perfect yet. For example: https://groups.google.com/forum/#!topic/golang-nuts/Kle874lT1Eo/discussion https://groups.google.com/forum/#!topic/golang-nuts/Kle874lT... -- Russ Cox: "The generator we're using only generates 63 bits worth of output. You're right that we probably should have corrected that before the API freeze. Oh well.")