You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tokenCategoryResultInput0 or capabilityInput0 can not be more specific than just bytes because they don't fit the bytesX type.
However in reality tokenCategoryResultInput0 is the union type of bytes0 | bytes32 | bytes33
and we know the type of capabilityInput0 to be 0x | 0x01 | 0x02 or more generic bytes0 | byte
but union types don't exist in CashScript and neither does bytes0 or as const typing
as an aside I noticed
The type byte has been removed. It was an alias of bytes1.
This issue is mainly just brainstorming about the type system for CashScript
tokenCategory example
consider the following example
tokenCategoryResultInput0
orcapabilityInput0
can not be more specific than justbytes
because they don't fit thebytesX
type.However in reality
tokenCategoryResultInput0
is the union type ofbytes0 | bytes32 | bytes33
and we know the type of
capabilityInput0
to be0x | 0x01 | 0x02
or more genericbytes0 | byte
but union types don't exist in CashScript and neither does
bytes0
oras const
typingas an aside I noticed
https://docs.soliditylang.org/en/v0.8.3/080-breaking-changes.html#silent-changes-of-the-semantics
The text was updated successfully, but these errors were encountered: