Linting rules
E029: incoming-messages-duplicate-opcode
Checks `contract` header field `incomingMessages` for duplicate message opcodes.
Metadata
Code:E029Rule:incoming-messages-duplicate-opcodeStatus: Stable sincev0.0.1Quick fix: not available
What it does
Checks contract header field incomingMessages for duplicate message opcodes.
Why is this bad?
If two incoming message variants share the same opcode, message decoding is ambiguous.
Example
struct (0x1000) MsgA {}
struct (0x1000) MsgB {}
contract Wallet {
incomingMessages: MsgA | MsgB,
}Use instead:
struct (0x1000) MsgA {}
struct (0x1001) MsgB {}Last updated on