There are cases in the standard library that explicitly intentionally return, or leave, invalid values in cases when they should not be used. This being the generalised case of this question.
One of the clearest examples (others don't necessarily have comments) of this is in go/types/initorder.go ``` 25496407 (Robert Griesemer 2015-04-06 18:23:51 -0700 294) x.index = -1 // for safety ``` This kind of behaviour is justified under the Rule of Repair: "When you must fail, fail noisily and as soon as possible." On Sat, 2017-04-01 at 00:33 +0200, 'Axel Wagner' via golang-nuts wrote: > > As this seems to be a not un-contentious issue and is also something > I > regularly suggest in code-reviews for colleagues to do, I would like > to > solicit further opinions on this; am I being unreasonable? Am I > recommending practices that makes worse go devs? > -- 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. For more options, visit https://groups.google.com/d/optout.
