Hi, All. it may be better to burn "skip()" in the fire of deprecation? and implement the "newSkip()" which by default will call the "read()", and then subclasses will provide its own fast/optimized implementation? Or we still tries to take care about all corner cases for "skip()"?
On 08/11/2018 19:01, Brent Christian wrote:
Some sort of disclaimer could frame the behavior being described, even if only something like, "skip() makes a best effort to account for a subclass's overridden skip() method behaving unexpectedly" -Brent
-- Best regards, Sergey.
