You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the same rational as in #1749, the calendar instance used during parsing in parseAsISO8601(...) could be reused across invocations.
What you think ?
The text was updated successfully, but these errors were encountered:
brenuart
changed the title
StdDateFormat: performance improvement of '_parseISO8601(...)'
StdDateFormat: performance improvement of '_parseAsISO8601(...)'
Aug 28, 2017
I think that might be a good idea. Looking at deserialization side I think DateFormat is actually cloned as well (first I thought it wasn't, but DeserializationContext.getDateFormat() does actually clone it), so reuse should be possible.
Still, I am almost tempted to attempt writing multi-threaded test just in case ... since failures wrt non-synchronized shared resources can be pretty nasty.
But there's bit of choreography still, wrt ensuring correct timezone and leniency settings are used (and perhaps Locale -- not 100% if it has any effect, but it is set on GregorianCalendar).
Following the same rational as in #1749, the calendar instance used during parsing in
parseAsISO8601(...)
could be reused across invocations.What you think ?
The text was updated successfully, but these errors were encountered: