-
Notifications
You must be signed in to change notification settings - Fork 341
Extract Method: isolate END_ELEMENT handling in computeNext() #2489
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.
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
Open
EmanuelAry
wants to merge
1
commit into
android:main
Choose a base branch
from
EmanuelAry:extract-method-EndElementResult
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+154
−124
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Performance & Code Quality Improvement: Eliminate
EndElementResultAllocationsThe
DexDumpIteratorclass is designed to parse very large XML files (~10-100MB) efficiently, as noted in the class-level JAVADOC. Introducing a newEndElementResultobject for every singleEND_ELEMENTevent (which can occur millions of times in a large file) introduces significant and unnecessary garbage collection pressure.Instead of creating a temporary result holder class to pass mutable state back and forth, we can promote
currentClass,currentMethod,annotationStack, andinConstructorto instance variables ofDexDumpIterator(similar to howcurrentPackageandcurrentLocationare already managed).This refactoring provides several key benefits:
EndElementResultallocations, significantly reducing GC overhead.handleEndElement(and potentially other helper methods) as they no longer need to accept or return these state variables.computeNext()becomes much cleaner, and we can restore the consistent 2-space indentation used throughout the rest of the file.