On Thu, 2 Oct 2025 13:24:25 GMT, Roger Riggs <[email protected]> wrote:
> And one more thought/question: The optionality of formatting is a parameter > used in the traversal of the formatting and parsing and affect nested > formatting calls. The DateTimePrintContext previously counts the depth of the > nesting with >0 indicating optional. It is the component that determines > (based on optional:true) whether an absent value throws. Was it considered to > change DateTimePrinterContext.optional to `final boolean optional` and create > a second instance with optional=true. > > Only the CompositePrinterParser changes the state to indicate that nested > PrinterParsers are optional. CompositePrinterParser could substitute the > optional DateTimePrintContext. That would be closer to the current design and > if allow it to be immutable. It seems strange that the formatting process creates a new DateTimePrintContext object. ------------- PR Comment: https://git.openjdk.org/jdk/pull/26913#issuecomment-3361262924
