-
Notifications
You must be signed in to change notification settings - Fork 418
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
I/O Design Meta-Issue #7954
Comments
Related: @benharsh has been looking at I/O overheads in the context of the revcomp benchmark and expects to put together a list of I/O issues / wishes in response to that exercise, as I understand it. |
Question: does anything in the release/examples/ directory rely on the functionality we intend to deprecate? |
My take on a rough prioritization of these tasks (grouped by coarse prioritization):
|
thanks @benharsh - I've reordered the issue description to reflect your suggestion. |
It might be good to keep a record of code style issues with the IO module here. See #14646 |
I recorded some documentation tasks related to IO on #14395, should I link them here as well? |
I think this issue should focus on things that fit into the API stabilization topic. Also this particular issue has things to address in a sorted order, so it might not make sense to try to add a big variety of small things to it. Perhaps linking other issues to the epic Stabilize core I/O routines #8639 is the right move. |
This issue is just meant to list and track I/O issues.
Priority Group 1
Priority Group 2
Priority Group 3
_
and we might consider renaming 'advance' to 'skip'channel.mark()
return the offset and throw if there is an error #13312Priority Group 4
The text was updated successfully, but these errors were encountered: