See IonValueLite.getFieldNameSymbol(): https://github.com/amazon-ion/ion-java/blob/master/src/main/java/com/amazon/ion/impl/lite/IonValueLite.java#L583
In this case, the symbol table is only retrieved once, so the parameterless variant of the method does not need a LazySymbolTableProvider at all. Although it seems like the JVM should be able to optimize away this allocation, we have profiles that show this not happening.
It looks like symbolValue(), stringValue() and getTypeAnnotationSymbols() could be similarly optimized.
See IonValueLite.getFieldNameSymbol(): https://github.com/amazon-ion/ion-java/blob/master/src/main/java/com/amazon/ion/impl/lite/IonValueLite.java#L583
In this case, the symbol table is only retrieved once, so the parameterless variant of the method does not need a LazySymbolTableProvider at all. Although it seems like the JVM should be able to optimize away this allocation, we have profiles that show this not happening.
It looks like
symbolValue(),stringValue()andgetTypeAnnotationSymbols()could be similarly optimized.