Skip to content

Implement type coercion rules #2

Description

@Arachnid

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions