3 ms·

The post is fun, thanks. I like Tim's idea of "taking the journey" with a programmer on discovering new content. It's certainly the best way to introduce the to

by Smerity 13y ago

The post is fun, thanks. I like Tim's idea of "taking the journey" with a programmer on discovering new content. It's certainly the best way to introduce the topic to others. All the potential sticking issues have been handled for you! I was also excited when he said "I filed a bug on June 6th, and it was fixed on the 12th. Gotta love that.". There is no better feeling than sending a pull request and having someone thank you, merge it, and fix the issue within a few hours or days of you sending it. In this case, however, I think his joy may be premature. Rob Pike replied to the bug saying it was indeed an issue and either the code or documentation should be fixed. Having Rob Pike reply is a good start, considering he's the primary author of Go. Someone else then came along and fixed it in a way the article's author is unhappy with, though[1]. [1]: https://code.google.com/p/go/issues/detail?id=5655 https://code.google.com/p/go/issues/detail?id=5655

unwind 13y ago
Yeah, the final comment on the bug is also from Mr Bray, and isn't exactly a "thanks". I was quite surprised by that combination after reading the diary blog post, they don't really match up.
- corresation 13y ago
  Agreed, that bug is quite a bit different from the impression in the blog post. Tim is completely right, however: Why can't he use the automatically differentiated leading underscore test? And the fix of the documentation is, as he mentioned, just as wrong as it already was. Now I wonder if his bug comment was sarcastic, because it would be had I written it.
  - BarkMore 13y ago
    Why can't he use the automatically differentiated leading underscore test? The go tool currently ignores all files with a leading '_' in the name. Changing the tool to use a file with the name '_test.go' complicates the rule for ignored files and might break an existing project. The workaround of using 'all_test.go' is not onerous.
- espadrine 13y ago
  That's because Tim Bray posted the blog post, after which he read the patch (the comment was submitted today).
zurn 13y ago
> Having Rob Pike reply is a good start, considering he's the primary author of Go According to himself and the Go FAQ he's just one member in the team, the beginnings are described as "Robert Griesemer, Rob Pike and Ken Thompson started sketching the goals for a new language on the white board on September 21, 2007"

by Smerity 13y ago

unwind 13y ago

Yeah, the final comment on the bug is also from Mr Bray, and isn't exactly a "thanks". I was quite surprised by that combination after reading the diary blog post, they don't really match up.

corresation 13y ago
Agreed, that bug is quite a bit different from the impression in the blog post. Tim is completely right, however: Why can't he use the automatically differentiated leading underscore test? And the fix of the documentation is, as he mentioned, just as wrong as it already was. Now I wonder if his bug comment was sarcastic, because it would be had I written it.
- BarkMore 13y ago
  Why can't he use the automatically differentiated leading underscore test? The go tool currently ignores all files with a leading '_' in the name. Changing the tool to use a file with the name '_test.go' complicates the rule for ignored files and might break an existing project. The workaround of using 'all_test.go' is not onerous.
espadrine 13y ago
That's because Tim Bray posted the blog post, after which he read the patch (the comment was submitted today).

zurn 13y ago

> Having Rob Pike reply is a good start, considering he's the primary author of Go According to himself and the Go FAQ he's just one member in the team, the beginnings are described as "Robert Griesemer, Rob Pike and Ken Thompson started sketching the goals for a new language on the white board on September 21, 2007"