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
I like these kinds of type notations which Rust also uses. But I also want to add some aliases for the i8, u8, i64 and u64 types; char, byte, int, uint.
Is this convention understandable @Utkub24, what do you think?
These types will also require a new integer parsing system that allows postfixes to the integers like u, u16, i32, etc... For example 34u16 will push a 16-bit unsigned integer that has the value 34.
I like these kinds of type notations which Rust also uses. But I also want to add some aliases for the i8, u8, i64 and u64 types; char, byte, int, uint.
Is this convention understandable @Utkub24, what do you think?
Just pick one and be consistent imo, the user can define aliases for them if they so desire.
Currently, the compiler only recognizes
int
intrinsic type. These should also be implemented:We should also update the load intrinsics so that they push the correct size of integer after reading. Same applies to the store intrinsics as well.
The text was updated successfully, but these errors were encountered: