Add EIP: Interface Naming Conventions

[pcaversaccio]

This specification defines a standardised way of naming interface functions, event or custom error definitions, or anything else included in an interface definition that is used as an identifier by compilers in some form.

[eth-bot]

File EIPS/eip-7182.md

Requires 1 more reviewers from @axic, @Pandapip1, @SamWilsn, @xinbenlv

[github-actions]

The commit 6f53822 (as a parent of 7101bf7) contains errors.
Please inspect the Run Summary for details.

[pcaversaccio]

quickly following up: any feedback @axic, @Pandapip1, @SamWilsn, @xinbenlv or can we get this merged since all tests pass?

[SamWilsn]

I am closing this pull request because we are in the process of separating EIPs and ERCs into distinct repositories. Unfortunately, as far as we are aware, GitHub does not provide any tools to ease this migration, so every pull request will need to be re-opened manually.

As this is a PR to create / modify an ERC, I will kindly ask you to redirect this to the new repository at ethereum/ERCs. We have prepared a guide to help with the process.

If there is relevant history here, please link to this PR from the new pull request.

On behalf of the EIP Editors, I apologize for this inconvenience.

[SamWilsn]

@pcaversaccio Sorry it's taken so long to get someone to take a look at this! From a first pass, I would say that this isn't a good fit for an EIP. I'd probably publish this as a standalone style guide.

---

Unless I'm misunderstanding the point? Maybe this is supposed to be a normalization step that compilers perform before generating the ABI and hashing interface ids / function selectors? If this is something that is supposed to be shared by all compilers, (1) I think that needs to be made more clear in the proposal, and (2) wouldn't this introduce a ton of backwards compatibility issues?