Add ability to keep track of only required Context Elements #267
Conversation
This file contains 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
suyashkumar
force-pushed
the
s/dataset-cache
branch
4 times, most recently
from
55b527a
to
bd4070d
Compare
This was referenced Apr 20, 2023
suyashkumar
force-pushed
the
s/dataset-cache
branch
from
bd4070d
to
e7dfaa4
Compare
suyashkumar
force-pushed
the
s/dataset-cache
branch
from
e7dfaa4
to
d8a7566
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 may reduce peak memory requirements if the user is using the Parser.Next() API and does not need the whole dataset in memory at once. That said, the element data probably isn't that signficiant compared to PixelData, so skipping reading the PixelData is probably the best way to go memory wise. This addresses #257.