New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entry drop
function can take a long time
#21
Comments
This is necessary to seek the reader to the header of the next entry. There is no |
I'm confused. I'm not familiar with the code but why don't we use Reader::seek here? |
|
@mdsteele WDYT about adding |
BTW what about calling |
Yes, it was written that way to avoid needing a I poked around just now, though, and it looks like |
The current drop implementation for
Entry
is as follows:When dealing with large entries, this function can take a very long time. Could there be a reason for this implementation? Do we really need to consume the reader?
The text was updated successfully, but these errors were encountered: