Fix external_calls_as_expressions to exclude builtins and library calls #2906
+169
−15
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.
Summary
--print function-summaryincorrectly reporting builtins and library calls as external callsDetails
The function-summary printer was incorrectly reporting all member access expressions as external calls. This includes:
abi.encode,msg.sender,block.timestampAddress.sendValue,SafeMath.addRoot cause
The original logic was:
This only checked if the call target was an
Identifier(internal call), but didn't account forMemberAccessexpressions that could be builtins or library calls.Fix
Added a helper function
_is_external_call()that properly classifies calls:Identifier-> internal call (not external)MemberAccesswhere expression isSolidityVariable-> builtin (not external)MemberAccesswhere expression is a libraryContract-> library call (not external)Test plan
Fixes #2073
🤖 Generated with Claude Code