Parses the text using this formatter, without resolving the result, intended
for advanced use cases.
Parsing is implemented as a two-phase operation.
First, the text is parsed using the layout defined by the formatter, producing
a
Map of field to value, a
ZoneId and a
Chronology.
Second, the parsed data is resolved, by validating, combining and
simplifying the various fields into more useful ones.
This method performs the parsing stage but not the resolving stage.
The result of this method is
TemporalAccessor which represents the
data as seen in the input. Values are not validated, thus parsing a date string
of '2012-00-65' would result in a temporal with three fields - year of '2012',
month of '0' and day-of-month of '65'.
The text will be parsed from the specified start
ParsePosition.
The entire length of the text does not have to be parsed, the
ParsePositionwill be updated with the index at the end of parsing.
Errors are returned using the error index field of the
ParsePositioninstead of
DateTimeParseException.
The returned error index will be set to an index indicative of the error.
Callers must check for errors before using the context.
If the formatter parses the same field more than once with different values,
the result will be an error.
This method is intended for advanced use cases that need access to the
internal state during parsing. Typical application code should use
#parse(CharSequence,TemporalQuery) or the parse method on the target type.