New in Go 1.20: wrapping multiple errors

Re:New in Go 1.20: wrapping multiple errors by masklinn on Sunday December 11, 2022 @08:59AM (#33943221)

> Of course, mnemonics 1-2-3-4-5-6-7 (1st month, 2nd day, 3rd hour, 4th minute, 5th second, 6-th year, 7th timezone) is harder to remember than mmHHMMssSSYYyy crap that is different in different languages.

Very much so. The latter is at least portable between cultures, because a month is a month, unlike "1".

And then of course you've got all the collisions like weekday (which for some reason does not follow the US standard either) or yearday, the ambiguities (like sub-seconds which can be either 0 or 9), and the outright missing fields (week numbers? week-years? No comprendo, señor..)

[ Parent | on HN ]

Re:New in Go 1.20: wrapping multiple errors by divan on Sunday December 11, 2022 @08:36PM (#33949818)

Very much so?

Let's put it to the pragmatic challenge. What will be the output of Go's "Jan 2006" and of R's "%B %h %M" format strings? Don't google.

[ Parent | on HN ]

Re:New in Go 1.20: wrapping multiple errors by masklinn on Monday December 12, 2022 @06:36AM (#33953562)

“Jan 2006” and short month, short month, minutes?

[ Parent | on HN ]

Re:New in Go 1.20: wrapping multiple errors by divan on Monday December 12, 2022 @08:37AM (#33954472)

To be clear "Jan 2006" - is a format string. Current date would yield "Dec 2022", obviously.

R example - it's "Long month, hour, decimal minute", so something like "December 15 35"

So you got Go format style right, and alphabet-style wrong. But Go's format is worse, right?

[ Parent | on HN ]