Custom error is described as "function() pure" instead of "error" in error messages in case of implicit conversions #13106

nishant-sachdeva · 2022-06-08T05:06:02Z

Description

Continued from #12896 . Created the issue as requested in #13005 (comment)

In custom errors like the following :

interface MyInterface {
    error MyCustomError();
}

The compiler mistakenly considers MyInterface.MyCustomError to be of type function() pure instead of type error. The latter is what should be used.

Running solc test.sol for the following code

interface MyInterface {
    error MyCustomError(uint256, bool);
}

contract Test {
    function test() public returns(bytes4) {
        return (MyInterface.MyCustomError);
    }
}

gives the following error

Error: Return argument type function (uint256,bool) pure is not implicitly convertible to expected type (type of first return variable) bytes4.
 --> test.sol:7:16:
  |
7 |         return (MyInterface.MyCustomError);
  |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^

The text was updated successfully, but these errors were encountered:

nishant-sachdeva added the bug 🐛 label Jun 8, 2022

nishant-sachdeva added this to New issues in Solidity via automation Jun 8, 2022

nishant-sachdeva mentioned this issue Jun 8, 2022

Display human readable type name in conversion error message #13005

Open

Custom error is described as "function() pure" instead of "error" in error messages in case of implicit conversions #13106

Custom error is described as "function() pure" instead of "error" in error messages in case of implicit conversions #13106

Comments

nishant-sachdeva commented Jun 8, 2022 • edited

Description

nishant-sachdeva commented Jun 8, 2022 •

edited