-
Notifications
You must be signed in to change notification settings - Fork 154
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
Provide an error to properly indicate EOF #246
Comments
This is a very popular request, and one that I fully support. Since it's a breaking API change it will come in version 0.6. :) |
Did I miss a duplicate ticket? I did look. How involved would this be? If the answer is "not very" I may be willing to help, but I barely have time for my own projects as it is. |
i think relevant would be #134 |
I've been working locally on some 0.6 features and have this prototyped. It works, though, there are some regressions I am ironing out. I'll push it to a 0.6 development branch once those issues are resolved. |
This has now been implemented in the |
I'm integrating Symphonia, and the only thing I can find on detecting EOF is the symphonia-play example, which is going as far as a string comparison on an error message. It seems like either FormatReader's next_packet should return
Option<Packet>
, or there should be a top-level error. Hopefully this isn't a duplicate of something or docs I'm missing.The text was updated successfully, but these errors were encountered: