public final class Instant extends Object implements Temporal, TemporalAdjuster, Comparable<Instant>, Serializable
This class models a single instantaneous point on the time-line. This might be used to record event time-stamps in the application.
The range of an instant requires the storage of a number larger than a long
. To achieve this, the class
stores a long
representing epoch-seconds and an int
representing nanosecond-of-second, which will
always be between 0 and 999,999,999. The epoch-seconds are measured from the standard Java epoch of
1970-01-01T00:00:00Z
where instants after the epoch have positive values, and earlier instants have negative
values. For both the epoch-second and nanosecond parts, a larger value is always later on the time-line than a
smaller value.
The length of the solar day is the standard way that humans measure time. This has traditionally been subdivided into 24 hours of 60 minutes of 60 seconds, forming a 86400 second day.
Modern timekeeping is based on atomic clocks which precisely define an SI second relative to the transitions of a Caesium atom. The length of an SI second was defined to be very close to the 86400th fraction of a day.
Unfortunately, as the Earth rotates the length of the day varies. In addition, over time the average length of the day is getting longer as the Earth slows. As a result, the length of a solar day in 2012 is slightly longer than 86400 SI seconds. The actual length of any given day and the amount by which the Earth is slowing are not predictable and can only be determined by measurement. The UT1 time-scale captures the accurate length of day, but is only available some time after the day has completed.
The UTC time-scale is a standard approach to bundle up all the additional fractions of a second from UT1 into whole seconds, known as leap-seconds. A leap-second may be added or removed depending on the Earth's rotational changes. As such, UTC permits a day to have 86399 SI seconds or 86401 SI seconds where necessary in order to keep the day aligned with the Sun.
The modern UTC time-scale was introduced in 1972, introducing the concept of whole leap-seconds. Between 1958 and 1972, the definition of UTC was complex, with minor sub-second leaps and alterations to the length of the notional second. As of 2012, discussions are underway to change the definition of UTC again, with the potential to remove leap seconds or introduce other changes.
Given the complexity of accurate timekeeping described above, this Java API defines its own time-scale, the Java Time-Scale.
The Java Time-Scale divides each calendar day into exactly 86400 subdivisions, known as seconds. These seconds may differ from the SI second. It closely matches the de facto international civil time scale, the definition of which changes from time to time.
The Java Time-Scale has slightly different definitions for different segments of the time-line, each based on the consensus international time scale that is used as the basis for civil time. Whenever the internationally-agreed time scale is modified or replaced, a new segment of the Java Time-Scale must be defined for it. Each segment must meet these requirements:
For the segment from 1972-11-03 (exact boundary discussed below) until further notice, the consensus international time scale is UTC (with leap seconds). In this segment, the Java Time-Scale is identical to UTC-SLS. This is identical to UTC on days that do not have a leap second. On days that do have a leap second, the leap second is spread equally over the last 1000 seconds of the day, maintaining the appearance of exactly 86400 seconds per day.
For the segment prior to 1972-11-03, extending back arbitrarily far, the consensus international time scale is defined to be UT1, applied proleptically, which is equivalent to the (mean) solar time on the prime meridian (Greenwich). In this segment, the Java Time-Scale is identical to the consensus international time scale. The exact boundary between the two segments is the instant where UT1 = UTC between 1972-11-03T00:00 and 1972-11-04T12:00.
Implementations of the Java time-scale using the JSR-310 API are not required to provide any clock that is sub-second
accurate, or that progresses monotonically or smoothly. Implementations are therefore not required to actually
perform the UTC-SLS slew or to otherwise be aware of leap seconds. JSR-310 does, however, require that
implementations must document the approach they use when defining a clock representing the current instant. See
Clock
for details on the available clocks.
The Java time-scale is used for all date-time classes. This includes Instant
, LocalDate
,
LocalTime
, OffsetDateTime
, ZonedDateTime
and Duration
.
This is a value-based class; use of identity-sensitive
operations (including reference equality (==
), identity hash code, or synchronization) on instances of
Instant
may have unpredictable results and should be avoided. The equals
method should be used for
comparisons.
This class is immutable and thread-safe.
Modifier and Type | Field and Description |
---|---|
static Instant |
EPOCH
Constant for the 1970-01-01T00:00:00Z epoch instant.
|
static Instant |
MAX
The maximum supported
Instant , '1000000000-12-31T23:59:59.999999999Z'. |
static Instant |
MIN
The minimum supported
Instant , '-1000000000-01-01T00:00Z'. |
Modifier and Type | Method and Description |
---|---|
Temporal |
adjustInto(Temporal temporal)
Adjusts the specified temporal object to have this instant.
|
OffsetDateTime |
atOffset(ZoneOffset offset)
Combines this instant with an offset to create an
OffsetDateTime . |
ZonedDateTime |
atZone(ZoneId zone)
Combines this instant with a time-zone to create a
ZonedDateTime . |
int |
compareTo(Instant otherInstant)
Compares this instant to the specified instant.
|
boolean |
equals(Object otherInstant)
Checks if this instant is equal to the specified instant.
|
static Instant |
from(TemporalAccessor temporal)
Obtains an instance of
Instant from a temporal object. |
int |
get(TemporalField field)
Gets the value of the specified field from this instant as an
int . |
long |
getEpochSecond()
Gets the number of seconds from the Java epoch of 1970-01-01T00:00:00Z.
|
long |
getLong(TemporalField field)
Gets the value of the specified field from this instant as a
long . |
int |
getNano()
Gets the number of nanoseconds, later along the time-line, from the start of the second.
|
int |
hashCode()
Returns a hash code for this instant.
|
boolean |
isAfter(Instant otherInstant)
Checks if this instant is after the specified instant.
|
boolean |
isBefore(Instant otherInstant)
Checks if this instant is before the specified instant.
|
boolean |
isSupported(TemporalField field)
Checks if the specified field is supported.
|
boolean |
isSupported(TemporalUnit unit)
Checks if the specified unit is supported.
|
Instant |
minus(long amountToSubtract,
TemporalUnit unit)
Returns a copy of this instant with the specified amount subtracted.
|
Instant |
minus(TemporalAmount amountToSubtract)
Returns a copy of this instant with the specified amount subtracted.
|
Instant |
minusMillis(long millisToSubtract)
Returns a copy of this instant with the specified duration in milliseconds subtracted.
|
Instant |
minusNanos(long nanosToSubtract)
Returns a copy of this instant with the specified duration in nanoseconds subtracted.
|
Instant |
minusSeconds(long secondsToSubtract)
Returns a copy of this instant with the specified duration in seconds subtracted.
|
static Instant |
now()
Obtains the current instant from the system clock.
|
static Instant |
now(Clock clock)
Obtains the current instant from the specified clock.
|
static Instant |
ofEpochMilli(long epochMilli)
Obtains an instance of
Instant using milliseconds from the epoch of 1970-01-01T00:00:00Z. |
static Instant |
ofEpochSecond(long epochSecond)
Obtains an instance of
Instant using seconds from the epoch of 1970-01-01T00:00:00Z. |
static Instant |
ofEpochSecond(long epochSecond,
long nanoAdjustment)
Obtains an instance of
Instant using seconds from the epoch of 1970-01-01T00:00:00Z and nanosecond
fraction of second. |
Instant |
plus(long amountToAdd,
TemporalUnit unit)
Returns a copy of this instant with the specified amount added.
|
Instant |
plus(TemporalAmount amountToAdd)
Returns a copy of this instant with the specified amount added.
|
Instant |
plusMillis(long millisToAdd)
Returns a copy of this instant with the specified duration in milliseconds added.
|
Instant |
plusNanos(long nanosToAdd)
Returns a copy of this instant with the specified duration in nanoseconds added.
|
Instant |
plusSeconds(long secondsToAdd)
Returns a copy of this instant with the specified duration in seconds added.
|
<R> R |
query(TemporalQuery<R> query)
Queries this instant using the specified query.
|
ValueRange |
range(TemporalField field)
Gets the range of valid values for the specified field.
|
long |
toEpochMilli()
Converts this instant to the number of milliseconds from the epoch of 1970-01-01T00:00:00Z.
|
Instant |
truncatedTo(TemporalUnit unit)
Returns a copy of this
Instant truncated to the specified unit. |
long |
until(Temporal endExclusive,
TemporalUnit unit)
Calculates the amount of time until another instant in terms of the specified unit.
|
Instant |
with(TemporalAdjuster adjuster)
Returns an adjusted copy of this instant.
|
Instant |
with(TemporalField field,
long newValue)
Returns a copy of this instant with the specified field set to a new value.
|
public static final Instant EPOCH
public static final Instant MAX
Instant
, '1000000000-12-31T23:59:59.999999999Z'. This could be used by an
application as a "far future" instant.
This is one year later than the maximum LocalDateTime
. This provides sufficient values to handle the
range of ZoneOffset
which affect the instant in addition to the local date-time. The value is also chosen
such that the value of the year fits in an int
.
public static final Instant MIN
Instant
, '-1000000000-01-01T00:00Z'. This could be used by an application as a "far
past" instant.
This is one year earlier than the minimum LocalDateTime
. This provides sufficient values to handle the
range of ZoneOffset
which affect the instant in addition to the local date-time. The value is also chosen
such that the value of the year fits in an int
.
public Temporal adjustInto(Temporal temporal)
This returns a temporal object of the same observable type as the input with the instant changed to be the same as this.
The adjustment is equivalent to using Temporal.with(TemporalField, long)
twice, passing
ChronoField.INSTANT_SECONDS
and ChronoField.NANO_OF_SECOND
as the fields.
In most cases, it is clearer to reverse the calling pattern by using Temporal.with(TemporalAdjuster)
:
// these two lines are equivalent, but the second approach is recommended temporal = thisInstant.adjustInto(temporal); temporal = temporal.with(thisInstant);
This instance is immutable and unaffected by this method call.
adjustInto
in interface TemporalAdjuster
temporal
- the target object to be adjusted, not nullDateTimeException
- if unable to make the adjustmentpublic OffsetDateTime atOffset(ZoneOffset offset)
OffsetDateTime
.
This returns an OffsetDateTime
formed from this instant at the specified offset from UTC/Greenwich. An
exception will be thrown if the instant is too large to fit into an offset date-time.
This method is equivalent to OffsetDateTime.ofInstant(this,
offset)
.
offset
- the offset to combine with, not nullDateTimeException
- if the result exceeds the supported rangepublic ZonedDateTime atZone(ZoneId zone)
ZonedDateTime
.
This returns an ZonedDateTime
formed from this instant at the specified time-zone. An exception will be
thrown if the instant is too large to fit into a zoned date-time.
This method is equivalent to ZonedDateTime.ofInstant(this,
zone)
.
zone
- the zone to combine with, not nullDateTimeException
- if the result exceeds the supported rangepublic int compareTo(Instant otherInstant)
The comparison is based on the time-line position of the instants. It is "consistent with equals", as defined by
Comparable
.
compareTo
in interface Comparable<Instant>
otherInstant
- the other instant to compare to, not nullNullPointerException
- if otherInstant is nullpublic boolean equals(@Nullable Object otherInstant)
The comparison is based on the time-line position of the instants.
equals
in class Object
otherInstant
- the other instant, null returns falseObject.hashCode()
,
HashMap
public static Instant from(TemporalAccessor temporal)
Instant
from a temporal object.
This obtains an instant based on the specified temporal. A TemporalAccessor
represents an arbitrary set
of date and time information, which this factory converts to an instance of Instant
.
The conversion extracts the INSTANT_SECONDS
and
NANO_OF_SECOND
fields.
This method matches the signature of the functional interface TemporalQuery
allowing it to be used as a
query via method reference, Instant::from
.
temporal
- the temporal object to convert, not nullDateTimeException
- if unable to convert to an Instant
public int get(TemporalField field)
int
.
This queries this instant for the value of the specified field. The returned value will always be within the valid range of values for the field. If it is not possible to return the value, because the field is not supported or for some other reason, an exception is thrown.
If the field is a ChronoField
then the query is implemented here. The supported fields
will return valid values based on this date-time, except INSTANT_SECONDS
which is too
large to fit in an int
and throws a DateTimeException
. All other ChronoField
instances
will throw an UnsupportedTemporalTypeException
.
If the field is not a ChronoField
, then the result of this method is obtained by invoking
TemporalField.getFrom(TemporalAccessor)
passing this
as the argument. Whether the value can be
obtained, and what the value represents, is determined by the field.
get
in interface TemporalAccessor
field
- the field to get, not nullDateTimeException
- if a value for the field cannot be obtained or the value is outside the range of valid values for the
fieldUnsupportedTemporalTypeException
- if the field is not supported or the range of values exceeds an int
public long getEpochSecond()
The epoch second count is a simple incrementing count of seconds where second 0 is 1970-01-01T00:00:00Z. The
nanosecond part of the day is returned by getNanosOfSecond
.
public long getLong(TemporalField field)
long
.
This queries this instant for the value of the specified field. If it is not possible to return the value, because the field is not supported or for some other reason, an exception is thrown.
If the field is a ChronoField
then the query is implemented here. The supported fields
will return valid values based on this date-time. All other ChronoField
instances will
throw an UnsupportedTemporalTypeException
.
If the field is not a ChronoField
, then the result of this method is obtained by invoking
TemporalField.getFrom(TemporalAccessor)
passing this
as the argument. Whether the value can be
obtained, and what the value represents, is determined by the field.
getLong
in interface TemporalAccessor
field
- the field to get, not nullDateTimeException
- if a value for the field cannot be obtainedUnsupportedTemporalTypeException
- if the field is not supportedpublic int getNano()
The nanosecond-of-second value measures the total number of nanoseconds from the second returned by
getEpochSecond
.
public int hashCode()
hashCode
in class Object
Object.equals(java.lang.Object)
,
System.identityHashCode(java.lang.Object)
public boolean isAfter(Instant otherInstant)
The comparison is based on the time-line position of the instants.
otherInstant
- the other instant to compare to, not nullNullPointerException
- if otherInstant is nullpublic boolean isBefore(Instant otherInstant)
The comparison is based on the time-line position of the instants.
otherInstant
- the other instant to compare to, not nullNullPointerException
- if otherInstant is nullpublic boolean isSupported(@Nullable TemporalField field)
This checks if this instant can be queried for the specified field. If false, then calling the
range
, get
and with(TemporalField, long)
methods will throw an exception.
If the field is a ChronoField
then the query is implemented here. The supported fields are:
NANO_OF_SECOND
MICRO_OF_SECOND
MILLI_OF_SECOND
INSTANT_SECONDS
ChronoField
instances will return false.
If the field is not a ChronoField
, then the result of this method is obtained by invoking
TemporalField.isSupportedBy(TemporalAccessor)
passing this
as the argument. Whether the field is
supported is determined by the field.
isSupported
in interface TemporalAccessor
field
- the field to check, null returns falsepublic boolean isSupported(@Nullable TemporalUnit unit)
This checks if the specified unit can be added to, or subtracted from, this date-time. If false, then calling the
plus(long, TemporalUnit)
and minus
methods will throw an exception.
If the unit is a ChronoUnit
then the query is implemented here. The supported units are:
NANOS
MICROS
MILLIS
SECONDS
MINUTES
HOURS
HALF_DAYS
DAYS
ChronoUnit
instances will return false.
If the unit is not a ChronoUnit
, then the result of this method is obtained by invoking
TemporalUnit.isSupportedBy(Temporal)
passing this
as the argument. Whether the unit is supported
is determined by the unit.
isSupported
in interface Temporal
unit
- the unit to check, null returns falsepublic Instant minus(long amountToSubtract, TemporalUnit unit)
This returns a Instant
, based on this one, with the amount in terms of the unit subtracted. If it is not
possible to subtract the amount, because the unit is not supported or for some other reason, an exception is
thrown.
This method is equivalent to plus(long, TemporalUnit)
with the amount negated. See that method for a
full description of how addition, and thus subtraction, works.
This instance is immutable and unaffected by this method call.
minus
in interface Temporal
amountToSubtract
- the amount of the unit to subtract from the result, may be negativeunit
- the unit of the amount to subtract, not nullInstant
based on this instant with the specified amount subtracted, not nullDateTimeException
- if the subtraction cannot be madeUnsupportedTemporalTypeException
- if the unit is not supportedpublic Instant minus(TemporalAmount amountToSubtract)
This returns an Instant
, based on this one, with the specified amount subtracted. The amount is typically
Duration
but may be any other type implementing the TemporalAmount
interface.
The calculation is delegated to the amount object by calling TemporalAmount.subtractFrom(Temporal)
. The
amount implementation is free to implement the subtraction in any way it wishes, however it typically calls back
to minus(long, TemporalUnit)
. Consult the documentation of the amount implementation to determine if it
can be successfully subtracted.
This instance is immutable and unaffected by this method call.
minus
in interface Temporal
amountToSubtract
- the amount to subtract, not nullInstant
based on this instant with the subtraction made, not nullDateTimeException
- if the subtraction cannot be madepublic Instant minusMillis(long millisToSubtract)
This instance is immutable and unaffected by this method call.
millisToSubtract
- the milliseconds to subtract, positive or negativeInstant
based on this instant with the specified milliseconds subtracted, not nullDateTimeException
- if the result exceeds the maximum or minimum instantpublic Instant minusNanos(long nanosToSubtract)
This instance is immutable and unaffected by this method call.
nanosToSubtract
- the nanoseconds to subtract, positive or negativeInstant
based on this instant with the specified nanoseconds subtracted, not nullDateTimeException
- if the result exceeds the maximum or minimum instantpublic Instant minusSeconds(long secondsToSubtract)
This instance is immutable and unaffected by this method call.
secondsToSubtract
- the seconds to subtract, positive or negativeInstant
based on this instant with the specified seconds subtracted, not nullDateTimeException
- if the result exceeds the maximum or minimum instantpublic static Instant now()
This will query the system UTC clock
to obtain the current instant.
Using this method will prevent the ability to use an alternate time-source for testing because the clock is effectively hard-coded.
public static Instant now(Clock clock)
This will query the specified clock to obtain the current time.
Using this method allows the use of an alternate clock for testing. The alternate clock may be introduced using
dependency injection
.
clock
- the clock to use, not nullpublic static Instant ofEpochMilli(long epochMilli)
Instant
using milliseconds from the epoch of 1970-01-01T00:00:00Z.
The seconds and nanoseconds are extracted from the specified milliseconds.
epochMilli
- the number of milliseconds from 1970-01-01T00:00:00ZDateTimeException
- if the instant exceeds the maximum or minimum instantpublic static Instant ofEpochSecond(long epochSecond)
Instant
using seconds from the epoch of 1970-01-01T00:00:00Z.
The nanosecond field is set to zero.
epochSecond
- the number of seconds from 1970-01-01T00:00:00ZDateTimeException
- if the instant exceeds the maximum or minimum instantpublic static Instant ofEpochSecond(long epochSecond, long nanoAdjustment)
Instant
using seconds from the epoch of 1970-01-01T00:00:00Z and nanosecond
fraction of second.
This method allows an arbitrary number of nanoseconds to be passed in. The factory will alter the values of the second and nanosecond in order to ensure that the stored nanosecond is in the range 0 to 999,999,999. For example, the following will result in the exactly the same instant:
Instant.ofEpochSecond(3, 1); Instant.ofEpochSecond(4, -999_999_999); Instant.ofEpochSecond(2, 1000_000_001);
epochSecond
- the number of seconds from 1970-01-01T00:00:00ZnanoAdjustment
- the nanosecond adjustment to the number of seconds, positive or negativeDateTimeException
- if the instant exceeds the maximum or minimum instantpublic Instant plus(long amountToAdd, TemporalUnit unit)
This returns an Instant
, based on this one, with the amount in terms of the unit added. If it is not
possible to add the amount, because the unit is not supported or for some other reason, an exception is thrown.
If the field is a ChronoUnit
then the addition is implemented here. The supported fields behave as
follows:
NANOS
- Returns a Instant
with the specified number of nanoseconds added. This is equivalent
to plusNanos(long)
.
MICROS
- Returns a Instant
with the specified number of microseconds added. This is
equivalent to plusNanos(long)
with the amount multiplied by 1,000.
MILLIS
- Returns a Instant
with the specified number of milliseconds added. This is
equivalent to plusNanos(long)
with the amount multiplied by 1,000,000.
SECONDS
- Returns a Instant
with the specified number of seconds added. This is equivalent to
plusSeconds(long)
.
MINUTES
- Returns a Instant
with the specified number of minutes added. This is equivalent to
plusSeconds(long)
with the amount multiplied by 60.
HOURS
- Returns a Instant
with the specified number of hours added. This is equivalent to
plusSeconds(long)
with the amount multiplied by 3,600.
HALF_DAYS
- Returns a Instant
with the specified number of half-days added. This is
equivalent to plusSeconds(long)
with the amount multiplied by 43,200 (12 hours).
DAYS
- Returns a Instant
with the specified number of days added. This is equivalent to
plusSeconds(long)
with the amount multiplied by 86,400 (24 hours).
All other ChronoUnit
instances will throw an UnsupportedTemporalTypeException
.
If the field is not a ChronoUnit
, then the result of this method is obtained by invoking
TemporalUnit.addTo(Temporal, long)
passing this
as the argument. In this case, the unit
determines whether and how to perform the addition.
This instance is immutable and unaffected by this method call.
plus
in interface Temporal
amountToAdd
- the amount of the unit to add to the result, may be negativeunit
- the unit of the amount to add, not nullInstant
based on this instant with the specified amount added, not nullDateTimeException
- if the addition cannot be madeUnsupportedTemporalTypeException
- if the unit is not supportedpublic Instant plus(TemporalAmount amountToAdd)
This returns an Instant
, based on this one, with the specified amount added. The amount is typically
Duration
but may be any other type implementing the TemporalAmount
interface.
The calculation is delegated to the amount object by calling TemporalAmount.addTo(Temporal)
. The amount
implementation is free to implement the addition in any way it wishes, however it typically calls back to
plus(long, TemporalUnit)
. Consult the documentation of the amount implementation to determine if it can
be successfully added.
This instance is immutable and unaffected by this method call.
plus
in interface Temporal
amountToAdd
- the amount to add, not nullInstant
based on this instant with the addition made, not nullDateTimeException
- if the addition cannot be madepublic Instant plusMillis(long millisToAdd)
This instance is immutable and unaffected by this method call.
millisToAdd
- the milliseconds to add, positive or negativeInstant
based on this instant with the specified milliseconds added, not nullDateTimeException
- if the result exceeds the maximum or minimum instantpublic Instant plusNanos(long nanosToAdd)
This instance is immutable and unaffected by this method call.
nanosToAdd
- the nanoseconds to add, positive or negativeInstant
based on this instant with the specified nanoseconds added, not nullDateTimeException
- if the result exceeds the maximum or minimum instantpublic Instant plusSeconds(long secondsToAdd)
This instance is immutable and unaffected by this method call.
secondsToAdd
- the seconds to add, positive or negativeInstant
based on this instant with the specified seconds added, not nullDateTimeException
- if the result exceeds the maximum or minimum instant@Nullable public <R> R query(TemporalQuery<R> query)
This queries this instant using the specified query strategy object. The TemporalQuery
object defines the
logic to be used to obtain the result. Read the documentation of the query to understand what the result of this
method will be.
The result of this method is obtained by invoking the TemporalQuery.queryFrom(TemporalAccessor)
method on
the specified query passing this
as the argument.
query
in interface TemporalAccessor
R
- the type of the resultquery
- the query to invoke, not nullDateTimeException
- if unable to query (defined by the query)
(defined by the query)public ValueRange range(TemporalField field)
The range object expresses the minimum and maximum valid values for a field. This instant is used to enhance the accuracy of the returned range. If it is not possible to return the range, because the field is not supported or for some other reason, an exception is thrown.
If the field is a ChronoField
then the query is implemented here. The supported fields
will return appropriate range instances. All other ChronoField
instances will throw an
UnsupportedTemporalTypeException
.
If the field is not a ChronoField
, then the result of this method is obtained by invoking
TemporalField.rangeRefinedBy(TemporalAccessor)
passing this
as the argument. Whether the range
can be obtained is determined by the field.
range
in interface TemporalAccessor
field
- the field to query the range for, not nullDateTimeException
- if the range for the field cannot be obtainedUnsupportedTemporalTypeException
- if the field is not supportedpublic long toEpochMilli()
If this instant represents a point on the time-line too far in the future or past to fit in a long
milliseconds, then an exception is thrown.
If this instant has greater than millisecond precision, then the conversion will drop any excess precision information as though the amount in nanoseconds was subject to integer division by one million.
public Instant truncatedTo(TemporalUnit unit)
Instant
truncated to the specified unit.
Truncating the instant returns a copy of the original with fields smaller than the specified unit set to zero.
The fields are calculated on the basis of using a UTC offset as seen in toString
. For example, truncating
with the MINUTES
unit will round down to the nearest minute, setting the seconds and
nanoseconds to zero.
The unit must have a duration that divides into the length of a standard
day without remainder. This includes all supplied time units on ChronoUnit
and DAYS
. Other units throw an exception.
This instance is immutable and unaffected by this method call.
unit
- the unit to truncate to, not nullInstant
based on this instant with the time truncated, not nullDateTimeException
- if the unit is invalid for truncationUnsupportedTemporalTypeException
- if the unit is not supportedpublic long until(Temporal endExclusive, TemporalUnit unit)
This calculates the amount of time between two Instant
objects in terms of a single TemporalUnit
.
The start and end points are this
and the specified instant. The result will be negative if the end is
before the start. The calculation returns a whole number, representing the number of complete units between the
two instants. The Temporal
passed to this method is converted to a Instant
using
from(TemporalAccessor)
. For example, the amount in days between two dates can be calculated using
startInstant.until(endInstant, SECONDS)
.
There are two equivalent ways of using this method. The first is to invoke this method. The second is to use
TemporalUnit.between(Temporal, Temporal)
:
// these two lines are equivalent amount = start.until(end, SECONDS); amount = SECONDS.between(start, end);The choice should be made based on which makes the code more readable.
The calculation is implemented in this method for ChronoUnit
. The units NANOS
, MICROS
,
MILLIS
, SECONDS
, MINUTES
, HOURS
, HALF_DAYS
and DAYS
are
supported. Other ChronoUnit
values will throw an exception.
If the unit is not a ChronoUnit
, then the result of this method is obtained by invoking
TemporalUnit.between(Temporal, Temporal)
passing this
as the first argument and the converted
input temporal as the second argument.
This instance is immutable and unaffected by this method call.
until
in interface Temporal
endExclusive
- the end date, exclusive, which is converted to an Instant
, not nullunit
- the unit to measure the amount in, not nullDateTimeException
- if the amount cannot be calculated, or the end temporal cannot be converted to an Instant
UnsupportedTemporalTypeException
- if the unit is not supportedpublic Instant with(TemporalAdjuster adjuster)
This returns an Instant
, based on this one, with the instant adjusted. The adjustment takes place using
the specified adjuster strategy object. Read the documentation of the adjuster to understand what adjustment will
be made.
The result of this method is obtained by invoking the TemporalAdjuster.adjustInto(Temporal)
method on the
specified adjuster passing this
as the argument.
This instance is immutable and unaffected by this method call.
with
in interface Temporal
adjuster
- the adjuster to use, not nullInstant
based on this
with the adjustment made, not nullDateTimeException
- if the adjustment cannot be madepublic Instant with(TemporalField field, long newValue)
This returns an Instant
, based on this one, with the value for the specified field changed. If it is not
possible to set the value, because the field is not supported or for some other reason, an exception is thrown.
If the field is a ChronoField
then the adjustment is implemented here. The supported fields behave as
follows:
NANO_OF_SECOND
- Returns an Instant
with the specified nano-of-second. The epoch-second will
be unchanged.
MICRO_OF_SECOND
- Returns an Instant
with the nano-of-second replaced by the specified
micro-of-second multiplied by 1,000. The epoch-second will be unchanged.
MILLI_OF_SECOND
- Returns an Instant
with the nano-of-second replaced by the specified
milli-of-second multiplied by 1,000,000. The epoch-second will be unchanged.
INSTANT_SECONDS
- Returns an Instant
with the specified epoch-second. The nano-of-second will
be unchanged.
In all cases, if the new value is outside the valid range of values for the field then a
DateTimeException
will be thrown.
All other ChronoField
instances will throw an UnsupportedTemporalTypeException
.
If the field is not a ChronoField
, then the result of this method is obtained by invoking
TemporalField.adjustInto(Temporal, long)
passing this
as the argument. In this case, the field
determines whether and how to adjust the instant.
This instance is immutable and unaffected by this method call.
with
in interface Temporal
field
- the field to set in the result, not nullnewValue
- the new value of the field in the resultInstant
based on this
with the specified field set, not nullDateTimeException
- if the field cannot be setUnsupportedTemporalTypeException
- if the field is not supported