-
Notifications
You must be signed in to change notification settings - Fork 102
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
Mapping between C# types and NeoVM types #290
Labels
Comments
Can someone check the implementation of the compiler according to this table? |
I will create a unit test in dev-pack for ensure this behaviour |
We should specify that the arguments are |
Maybe we should add an |
Yes, I will |
fix it #295 |
lightszero
added a commit
that referenced
this issue
Jun 17, 2020
fixed #290 Co-authored-by: lights li <lightsever@hotmail.com> Co-authored-by: erikzhang <erik@neo.org>
ProDog
pushed a commit
to ProDog/neo-devpack-dotnet
that referenced
this issue
Jun 22, 2020
fixed neo-project#290 Co-authored-by: lights li <lightsever@hotmail.com> Co-authored-by: erikzhang <erik@neo.org>
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Supported types
C# -> NeoVM
null -> Null
bool -> Integer
sbyte -> Integer
byte -> Integer
short -> Integer
ushort -> Integer
int -> Integer
uint -> Integer
long -> Integer
ulong -> Integer
BigInteger -> Integer
byte[] -> Buffer
char -> Integer
string -> ByteString
Array -> Array
Enum -> Integer
class -> Array
struct -> Struct
tuple -> Struct
event -> System.Runtime.Notify()
lambda -> Pointer
Delegate -> Pointer | Callback
Any nullable types will also be mapped to the NeoVM types corresponding to their base types. Because all NeoVM types are nullable.
Unsupported types
float
double
decimal
The text was updated successfully, but these errors were encountered: