-
Notifications
You must be signed in to change notification settings - Fork 34
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
[WIP] EIP-50 - 6.0 Soft-Fork #100
base: master
Are you sure you want to change the base?
Conversation
|
||
* support MethodCall encoding of Numeric methods | ||
|
||
issue: https://github.com/ScorexFoundation/sigmastate-interpreter/issues/667 |
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.
Maybe this is not necessary. Looking back is was not good idea to allow both method call
and opcode
encoding for methods. It would be better to forbid method calls for those methods which have dedicated opcodes.
The translation MC -> opcode is actually happens in the compiler, but is not strictly enforced. This creates more surface for test coverage and potential bugs.
* Add roundtrip test in *MethodCallSerializerSpecification* | ||
|
||
* Add evaluation test (see "nbits evaluation" test) | ||
|
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.
* For each new method separate property tests should be added to SigmaDslSpecification. |
No description provided.