-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
read! doesn't work in v2.0.0? #95
Comments
Hi. I simply looked at
|
@banhbio You are completely right, this is a bug. I've made fix, added tests so it doesn't regress in the future, and will release version 2.0.1 with the fix in a few hours. For what it's worth, in version 2, it's preferred to use a regular for loop to iterate over readers: for record in reader
[do something]
end Instead of the old record = FASTQ.Record()
while !eof(reader)
read!(reader, record)
[do something]
end In 99% of cases, the slight performance boost of the latter will not matter. When it does matter, you can initialize the reader with the keyword |
@jakobnissen Thanks for your response and great advice! |
Thank you for building a nice package.
When I migrated from FASTX.jl v1.3.0 to v2.0.0, an error occurred due to the behavior of
read!
I couldn't find any docs or tests on
read!
in v2.0.0, so I'm confused about whether this is a deprecated or a bug.Expected Behavior
In v1.3.0
returns
Current Behavior
But, in v2.0.0, the code above returns nothing.
Steps to Reproduce (for bugs)
I got the test file from here
Context
In
./src/fastq/reader.jl
,read!
seems to do nothing forrec
.Is it expected behavior or a bug?
best.
The text was updated successfully, but these errors were encountered: