Why Doesn\'t Go\'s `time.Parse()` Handle Timezone Identifiers?

Why Go's time.Parse() Doesn't Parse Timezone Identifiers

In Go, the time.Parse() function is used to parse a date and time string into a Time value. However, unlike other date and time libraries, time.Parse() does not automatically parse timezone identifiers like "EST" or "EDT". Instead, it uses the current system's timezone to determine the offset for the time.

The Problem

The code provided in the question demonstrates this issue. It attempts to parse a date string ("2018 08 01 12:00 EDT") using time.Parse() in two ways: with and without specifying the desired timezone location (America/New_York).

When using time.Parse() without specifying a location, the timezone identifier ("EDT") is not recognized, and the time is parsed as being in the current system's timezone (" 0000"). This results in an incorrect time value.

The Solution

To correctly parse a date and time string that includes a timezone identifier, the time.ParseInLocation() function must be used. This function takes an additional Location parameter, which specifies the desired timezone for the parsed time.

In the code provided, time.LoadLocation() is used to create a Location object for the desired timezone ("America/New_York") before passing it to time.ParseInLocation(). This ensures that the timezone identifier ("EDT") is correctly parsed and the correct time value is returned.

Alternative Solutions

Alternatively, one can use a date and time library that explicitly supports timezone parsing, such as the popular "time.go" library. This library provides functions like ParseInZone(), which allow for direct parsing of timezone identifiers.

The above is the detailed content of Why Doesn\'t Go\'s `time.Parse()` Handle Timezone Identifiers?. For more information, please follow other related articles on the PHP Chinese website!