Michael Macias

> For the latter case, we could also add a `fn index(src: P) -> io::Result` convenience function, if that would be useful. @nh13, this is added in noodles 0.58.0 /...

See also #70, a long-standing issue noting this: > It is clear from examination of .csi files that they are stored as BGZF (why?), although this is not mentioned and...

Hi @KuechlerO, Do you mean that FASTX is not allowing a missing newline at EOF? Can you share an example of a record that is passing fq lint but failing...

Text lines typically have two interpretations: they can either be terminated by a newline, as [defined in POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206), or separated by one, as in your case. Most line readers support...

Can you ensure your inputs are indeed not corrupt? I.e., `gzip --verbose --test XXX_1.merged.fastq.gz XXX_2.merged.fastq.gz`.

There is indeed no consensus on how fixed-sized character arrays are encoded/decoded. I'll try to push samtools/hts-specs#631 to see if can be resolved first. As a workaround in noodles, you...

Thanks for reporting, @apraga. This case is undefined in VCF 4.1/4.2. I asked for clarification in https://github.com/samtools/hts-specs/issues/760.

This behavior remains undefined, but for inputs that are VCF < 4.3, noodles will now read other header record values that start with a map prefix (`= 4.3 and will...

I believe the type system resolves any coordinate system ambiguity. All positions in noodles are normalized to be 1-based, wrapped by, as you mentioned, [`core::Position`](https://docs.rs/noodles/0.61.0/noodles/core/struct.Position.html). The 1-based coordinate system, [by...

`fq lint` does not provide an output. Its usage is meant to be either be a success or failure, signaled by the process's exit code. `stdout` only contains simple log...