Support named parameters in abi.encodeCall

[Amxx]

Abstract

Add support for the following syntax:

abi.encodeCall(fnPointer, { arg1: 1, arg2: 2 });

Motivation

It is currently possible to call a function, or throw a custom error, using this syntax:

target.fn({ arg1: 1, arg2: 2 });
revert E({ arg1: 1, arg2: 2 });

it would be nice to have the same syntax supported for abi.encodeCall

Specification

The compiler already know how to encode the call when doing target.fn({ arg1: 1, arg2: 2 });. The idea is to reuse the same argument encoding logic, and return the encoded data without performing the call

Backwards Compatibility

No issue.

[github-actions]

This issue has been marked as stale due to inactivity for the last 90 days.
It will be automatically closed in 7 days.