- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
This can be easily solved by just specifying a custom format string instead of one of the predefined constants.
t.AppendFormat(l.bufStream[:0], "2005-01-02T15:04:05.999999999Z")
(the other WTF is Go's use of a "reference date" to specify a date format string, but I've grown to like it)
Admin
correction...
This can be easily solved by just specifying a custom format string instead of one of the predefined constants.
t.AppendFormat(l.bufStream[:0], "2006-01-02T15:04:05.000000000Z")
(the 0's at the end indicate fixed decimal places using trailing zeroes; nines would represent decimals with no trailing zeroes)
Edit Admin
Perhaps not, but it is very close to wrong, on the basis that one of the reasons for the success of things like Python (and others) is the amount of stuff you can do using just the standard library.
Admin
It's short for: Go build your own libraries!
Edit Admin
As a counterpoint: what ends up in the class library is harder to change and you can get trapped. Third parties have a harder time getting traction in domains where the standard library has an implementation, even if that implementation is bad. Time and dates prior to Java 8 are a good example, and the C++ STL is an evergreen case.