UTC, Coordinated Universal Time, is not really an arbitrary time zone. It's
the time scale underlying almost all time measurements on Earth (excepting
some specific use cases, typically in astronomy) and from which all time
zones are derived. As such, I don't think it implies a location (other than
>
> > The sec and nsec fields in a time.Time are relative to the Unix epoch
> and so
> > denote a point in time by themselves. The location is merely for
> > presentation.
>
> Pedantically, they are not relative to the Unix epoch. They are
> relative to January 1, year 1, 00:00:00.0
I am aware. I don't understand how that contradicts my point that they have
an implied location (or rather *Location, namely time.UTC).
I am aware, that you could choose an arbitrary *Location (because that's
what time.UTC is. Just one, arbitrary, timezone) and create a special
in-memory Represent
On Wed, Sep 21, 2016 at 1:55 PM, Jakob Borg wrote:
> The sec and nsec fields in a time.Time are relative to the Unix epoch and so
> denote a point in time by themselves.
Right, making your "instant" a duration with an implicit starting
time, and a time that has a timezone at that (aka, just a dur
Ah, indeed. No pedantry required to appreciate the difference, it's almost
two thousand years after all. :) Sorry for the confusion.
//jb
ons 21 sep. 2016 kl 21:40 skrev Ian Lance Taylor :
> On Wed, Sep 21, 2016 at 11:55 AM, Jakob Borg wrote:
> > The sec and nsec fields in a time.Time are relat
On Wed, Sep 21, 2016 at 11:55 AM, Jakob Borg wrote:
> The sec and nsec fields in a time.Time are relative to the Unix epoch and so
> denote a point in time by themselves. The location is merely for
> presentation.
Pedantically, they are not relative to the Unix epoch. They are
relative to Januar
The sec and nsec fields in a time.Time are relative to the Unix epoch and
so denote a point in time by themselves. The location is merely for
presentation.
ons 21 sep. 2016 kl 20:35 skrev 'Axel Wagner' via golang-nuts <
golang-nuts@googlegroups.com>:
> Your Instant is not an Instant, it's a durat
Your Instant is not an Instant, it's a duration. For a duration to
demarkate an Instant, you'd actually need a reference point (a zero). And
that'll pretty much certainly be given relative to a location. So even your
Instant still has a location, it's just implied (probably to be UTC).
Personally,
On Wed, Sep 21, 2016 at 11:22 AM, Paul Jolly wrote:
> Please can someone can enlighten me or point me towards relevant docs/other
> regarding the design decisions behind time.Time?
>
> Specifically why the concept of an instant in time, referenced many times
> throughout the time docs, was not enc
Please can someone can enlighten me or point me towards relevant docs/other
regarding the design decisions behind time.Time?
Specifically why the concept of an instant in time, referenced many times
throughout the time docs, was not encoded as a type itself:
type Instant struct {
sec int64
10 matches
Mail list logo
