Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create a unified approach to skipped/unparsed offset tracking #84

Open
d0c-s4vage opened this issue Oct 1, 2019 · 0 comments
Open

Create a unified approach to skipped/unparsed offset tracking #84

d0c-s4vage opened this issue Oct 1, 2019 · 0 comments

Comments

@d0c-s4vage
Copy link
Owner

d0c-s4vage commented Oct 1, 2019 •
edited
Loading

Individual unparsed offsets from an input stream should only be represented ONCE in a _skipped field, even if data was skipped over multiple times.

See #82 for additional backstory
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@d0c-s4vage