Skip to content

Optimize JsonParser.getDoubleValue()/getFloatValue()/getDecimalValue() to avoid String allocation #1284

@cowtowncoder

Description

@cowtowncoder

With #1230 done, we can tackle one problem that may have been a regression: the fact that even when following JsonParser methods are used:

  • getDecimalValue()
  • getDoubleValue()
  • getFloatValue()

there will still be a String allocation even if that is not really needed for deferred decoding (like JsonParser.getNumberValueDeferred())
This may be a regression to address other problems with too-early binding of type.

Metadata

Metadata

Assignees

No one assigned

    Labels

    2.18Issues planned at earliest for 2.18performanceIssue related to performance problems or enhancements

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions