Fix call-graph printer to distinguish overloaded functions

[ep0chzer0]

Summary

Fixes #664

The call-graph printer was using just function.name for node IDs and labels, causing overloaded functions (same name, different signatures) to appear as the same node. This made it look like functions were calling themselves when they were actually calling an overloaded variant.

Problem

For the SafeMath library example in the issue:

function sub(uint256 a, uint256 b) internal pure returns (uint256) {
    return sub(a, b, "SafeMath: subtraction overflow");
}

function sub(uint256 a, uint256 b, string memory errorMessage) internal pure returns (uint256) {
    require(b <= a, errorMessage);
    return a - b;
}

The graph showed sub → sub, making it look like a self-call.

Solution

• Use function.full_name (includes parameter types) for node IDs to ensure each overloaded function gets a unique node
• Use function.full_name for labels so users can distinguish between overloaded functions in the graph
• Use function.solidity_signature for Variables (public state variables) to maintain consistency

Before/After

Before:

"SafeMath.sub" -> "SafeMath.sub"

After:

"SafeMath.sub(uint256,uint256)" -> "SafeMath.sub(uint256,uint256,string)"

Test Plan

• Verify overloaded functions get unique node IDs
• Verify labels show full signatures
• Run black formatter

🤖 Generated with Claude Code

[ep0chzer0]

Hello maintainers! This fixes the long-standing issue where overloaded functions appeared as self-calls in the call graph. The fix uses full_name instead of just name for node IDs and labels. Could you please approve the CI workflows to run? Thank you!