Track `record_pos` in state
Opened this issue · 0 comments
bovee commented
And have it reportable via StateMetadata? This would allow e.g. MS parsers to return the current "scan" record position in errors instead of how many individual m/z's they've spit out and may also make sense for e.g. kmer-based parsing.