Resolve parser ambiguity#5
Open
jakobnissen wants to merge 3 commits into
Open
Conversation
CiaranOMara
force-pushed
the
develop
branch
5 times, most recently
from
7a01eec to
781b688
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I want to push BioJulia/Automa.jl#49, and am in the process of checking all packages that depend on Automa for whether that commit introduces errors.
In BigBed, it's not possible for the parser to determine whether a record like
b"\0\0\0\1\0\0\0\1\0\0\0\1\0"contains a name or not, and the actions it should take are therefore ambiguous.This change fixes that.