I did. It fails to parse dates with two digits for the month or day. On Monday, June 9, 2025 at 12:05:26 PM UTC-7 burak serdar wrote:
> > > On Mon, Jun 9, 2025, 10:00 PM David Karr <davidmic...@gmail.com> wrote: > >> I've used "time.Parse()" several times in various small applications, and >> today I realized a curious inflexibility with it. If I have to parse date >> values where the months or days could be either 1 or 2 digits, which is all >> cases if the code might be dealing with dates anywhere in the year, then I >> have no choice but to implement a "normalize" function that adds a "0" at >> the start if the value is not two digits. I got this to work, but anyone >> who uses this method would have to write the same code. It seems odd that >> this wouldn't be handled automatically. > > > > Did you try single digit for day and month in the format? > >> -- >> 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...@googlegroups.com. >> To view this discussion visit >> https://groups.google.com/d/msgid/golang-nuts/5f201757-f548-4374-958b-034b5c15473dn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/golang-nuts/5f201757-f548-4374-958b-034b5c15473dn%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/3c3ea585-0b1e-4f37-ac1c-a0163e7727dbn%40googlegroups.com.