to != callee in transferAndCall() and transferMultipleAndCall()?

[IaroslavMazur]

Here are the current signatures of the transferAndCall() and transferMultipleAndCall() INativeTokens functions:

function transferAndCall(
        address from,
        address to,
        bytes32 tokenID,
        uint256 amount,
        address callee,
        bytes calldata data
    )
        external;

    function transferMultipleAndCall(
        address from,
        address[] calldata to,
        bytes32[] calldata tokenIDs,
        uint256[] calldata amounts,
        address callee,
        bytes calldata data
    )
        external;

Shouldn't we only allow transferring the tokens to the very contract you're calling, though?

What's the point of transferring the tokens to one address, but calling another one?

[IaroslavMazur]

Ended up implementing it the way I've proposed in the OP.

@PaulRBerg, can we close this discussion?

[PaulRBerg]

Awesome! Yeah let's close it.