It is for null, true and false but recall we had a bug due to that even if no more sure which one.
What is slow exactly? Isnt it inlined at some point? Or do we call it too often? (fix is different ;). Le mer. 31 juil. 2019 à 18:57, Mark Struberg <strub...@yahoo.de.invalid> a écrit : > hi folks! > > We have quite some JsonValue.NULL.equals(...) in our code. > Seems this part is slow according to YourKit. > > Wouldn't it be perfectly enough to use JsonValue.NULL == ? > > LieGrue, > strub > >
