Re:Go 1.10 Release Notes
by kasey_junk on Friday February 16, 2018 @06:55PM
(#16397768)
There are lots of things on my list you could do that were simple & effective that would provide me more value than this.
Historically the argument against them have been about adding needless complexity. I wonder who was asking for this and how they got it prioritized.
It was requested by rsc in 2015: https://github.com/golang/go/issues/11193
It was implemented by rsc subsequently, after discussion on the issue: https://go-review.googlesource.com/c/go/+/75631
I'm not sure what you're trying to insinuate.
Re:Go 1.10 Release Notes
by kasey_junk on Friday February 16, 2018 @07:49PM
(#16398073)
I’m not insinuating anything. I’m flat saying this seems like a low value feature. Other higher value features are denied on the basis of unneeded complexity.
I mean, the project lead wanted a feature and then implemented the feature, clearly it had value to him.
The difference is that this feature (ideally) only affects implementation complexity, not interface complexity. It can also be dropped again tomorrow without breaking the world.
This makes it wildly different from language changes, which require a lot more consideration.
Before 1.10 `go test` used to re-run tests unconditionally.
Since 1.10 it'll avoid re-running them in some cases.
Neither me nor the announcement claims "intelligence".
The rules are simple and effective which is the Go Way.
While you could try to make even better, more "intelligent" rules for determining wether to re-run the tests, those would quickly run into engineering complexity chasing diminishing returns. That is not the Go Way.