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

Implement type coercion rules #2

Open
Arachnid opened this issue Jun 15, 2021 · 1 comment
Open

Implement type coercion rules #2

Arachnid opened this issue Jun 15, 2021 · 1 comment

Comments

@Arachnid
Copy link
Contributor

Right now we simply fail if you try and pass a return value of one type as an argument to another function, but we should probably understand that some types of casts (like bytes to string and bytes32 to uint256) are okay. Or we could demand explicit typecasts for types that are binary-compatible, for safety?

@BlinkyStitt
Copy link

explicit typecasts sounds safest to me. Solidity itself has gone that route.

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

2 participants