-
Notifications
You must be signed in to change notification settings - Fork 649
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
unsigned_int unpacking #1267
unsigned_int unpacking #1267
Conversation
@@ -122,7 +122,6 @@ template<> struct js_name<fc::uint160> { static std::string name(){ retu | |||
template<> struct js_name<fc::sha224> { static std::string name(){ return "bytes 28"; } }; | |||
template<> struct js_name<fc::sha256> { static std::string name(){ return "bytes 32"; } }; | |||
template<> struct js_name<fc::unsigned_int> { static std::string name(){ return "varuint32"; } }; | |||
template<> struct js_name<fc::signed_int> { static std::string name(){ return "varint32"; } }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually JS code is using varint32
everywhere but not varuint32
. Will submit an issue there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, should we rename that to varuint64?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think so.
JS code need to be fixed anyway.
Restarted. |
Resolves #993 and #1088.
TODO: