End-Of-Image markers for more robust Progressive JPEG decoding #835
+155
−38
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.
This PR does a few things:
progressive.jpeg
image were passing). Added another imagetricky_progressive.jpeg
which trips up the decoder and requires those markers. Cross-checked withlibjpeg
end it also needs EOI markers.Data.firstIndex
which seems to give a decent speed up. Also triedData.range(of:)
but that was slower.