Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review approach to fully qualified function names #13

Closed
fulldecent opened this issue Jul 13, 2019 · 2 comments
Closed

Review approach to fully qualified function names #13

fulldecent opened this issue Jul 13, 2019 · 2 comments

Comments

@fulldecent
Copy link
Owner

This project introduces a convention that function names and events will be fully qualified. E.g. AIP010Transferred, aip010TokenURI.

The intent is to encourage composability and prevent naming conflicts. Also this obviates the supportsInterface technique from ERC-165 and relies on Aion's superior function calling ability (i.e. function names are not hashing, resulting in collisions).

Seeking input from other AIP authors if this should be best practice.

@fulldecent
Copy link
Owner Author

Reviewed with Aion team. Decision is to proceed with prefixed function and events names for AIP standards.

Reference: phone meeting 2019-08-02 with @jeff-aion and @jennjiuju.

@fulldecent
Copy link
Owner Author

Mentioning interested party: @satran004 from aionnetwork/AIP#40 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant