[FEATURE] Return value and follow args - optimization #75
Merged
hasherezade merged 2 commits intohasherezade:masterfrom Jun 4, 2025
Merged
[FEATURE] Return value and follow args - optimization #75hasherezade merged 2 commits intohasherezade:masterfrom
hasherezade merged 2 commits intohasherezade:masterfrom
Conversation
Owner
|
Thank you for your work! It is right on time for the new release that I am preparing :) |
Owner
|
@maxspl - I tested it and made some minor changes. I think it is a super cool feature that will benefit many people 🔥 |
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.
Hi !
As discussed in #70, the feature to follow args change has been modified:
Before: Args of function calls were tracked even after the function returned.
After: Args of function calls are tracker until the function returned.
Like I mentioned in the discussion: the code has been considerably simplified, but I still had to use stack storage to store function call details. I could have kept only the last call but the stack storage allows to track nested calls (currently I don't see if there's a configuration of the tool that would allow this but just in case, I chose this approach).
Thanks !