Remove ByteBuddy indirection in ExecutionFlowFrameVisitor - #1575
Draft
ptziegler wants to merge 1 commit into
Draft
Remove ByteBuddy indirection in ExecutionFlowFrameVisitor#1575ptziegler wants to merge 1 commit into
ptziegler wants to merge 1 commit into
Conversation
ptziegler
marked this pull request as draft
August 10, 2026 20:34
We use ByteBuddy to "augment" the visitor when traversing generic statements. This approach is time/memory intensive, as we need to create and load a new class, every time the Java file is parsed, but also difficult to debug, as the generated byte code lacks any meaningful debug information. Instead the logic is embedded directly into the base visitor and dynamically enabled when this complex behavior is required.
ptziegler
force-pushed
the
bytebuddy-cleanup
branch
from
August 10, 2026 21:40
c39ac95 to
560469d
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
1 participant
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.
We use ByteBuddy to "augment" the visitor when traversing generic statements. This approach is time/memory intensive, as we need to create and load a new class, every time the Java file is parsed, but also difficult to debug, as the generated byte code lacks any meaningful debug information.
Instead the logic is embedded directly into the base visitor and dynamically enabled when this complex behavior is required.