You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"The Go date format is one my huge annoyances about the language (not generics, interface{} magic, or the lack of immutable types). My biggest issue is that despite the fact the designers call Strftime bad because no one remembers the letters, and has to have documentation handy - the Go docs don't even document the magic numbers you have to use.
Why 2006? How do I represent a day? When do I use _2 vs 2? Its very poorly documented and thankfully all I use is RFC3339 and Unix timestamps."
The text was updated successfully, but these errors were encountered:
"The Go date format is one my huge annoyances about the language (not
generics, interface{} magic, or the lack of immutable types). My biggest
issue is that despite the fact the designers call Strftime bad because no
one remembers the letters, and has to have documentation handy - the Go
docs don't even document the magic numbers you have to use.
Why 2006? How do I represent a day? When do I use _2 vs 2? Its very poorly
documented and thankfully all I use is RFC3339 and Unix timestamps."
—
Reply to this email directly or view it on GitHub #9689.
As documented in this hacker news thread:
https://news.ycombinator.com/item?id=8944578
"The Go date format is one my huge annoyances about the language (not generics, interface{} magic, or the lack of immutable types). My biggest issue is that despite the fact the designers call Strftime bad because no one remembers the letters, and has to have documentation handy - the Go docs don't even document the magic numbers you have to use.
Why 2006? How do I represent a day? When do I use _2 vs 2? Its very poorly documented and thankfully all I use is RFC3339 and Unix timestamps."
The text was updated successfully, but these errors were encountered: