Although there are theoretical performance benefits from implementing JsonParser.nextTextValue(), the sheer complexity of implementation for CBOR backend makes it a bad trade-off. So let's just drop it from 2.15.0, to avoid hiding subtle bugs that may cause production issues.
(due to #372 )
Although there are theoretical performance benefits from implementing
JsonParser.nextTextValue(), the sheer complexity of implementation for CBOR backend makes it a bad trade-off. So let's just drop it from 2.15.0, to avoid hiding subtle bugs that may cause production issues.