-
Notifications
You must be signed in to change notification settings - Fork 716
Refactor cost calculation to accept multiple size inputs #2152
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
Refactor cost calculation to accept multiple size inputs #2152
Conversation
160b2e9 to
0b906b9
Compare
6643167 to
398a500
Compare
kantai
left a comment
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.
LGTM!
jcnelson
left a comment
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.
I'm having a hard time seeing how the user-defined cost function's arguments are generated. Can you point me to where that happens?
@jcnelson Is this what you're looking for? |
jcnelson
left a comment
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.
LGTM!
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Refactor the
runtime_costfunction to take aVec<u64>instead of a singleu64, thus enabling Clarity cost functions to take multiple size input args.