incorrect go-to-implementation for overloaded function

[0xalpharush]

When I go click go-to-definition on the following overloaded example, it points at the incorrect function definition and makes it appear as a recursive call (notice the number of parameters is different).

contract X {
    function overload(
        address _a,
        address _b,
        address _c,
        address _d,
        uint256 _e,
        uint256 _f,
        bytes memory _data
    ) internal returns (uint256) {
        return
            overload(
                _a,
                _b,
                _c,
                _d,
                msg.sender,
                _e,
                _f,
                _data
            );
    }
    function overload(
    address _a,
    address _b,
    address _c,
    address _d,
    address,
    uint256 _e,
    uint256 _f,
    bytes memory _data
) internal returns (uint256) {

}


}