Skip to content

Conversation

@reedrosenbluth
Copy link
Contributor

Refactor the runtime_cost function to take a Vec<u64> instead of a single u64, thus enabling Clarity cost functions to take multiple size input args.

@reedrosenbluth reedrosenbluth changed the base branch from master to feat/cost-contract-integration December 10, 2020 22:06
@reedrosenbluth reedrosenbluth force-pushed the feat/compute-cost-multiple-inputs branch 2 times, most recently from 160b2e9 to 0b906b9 Compare December 11, 2020 03:21
@reedrosenbluth reedrosenbluth marked this pull request as ready for review December 11, 2020 16:04
@reedrosenbluth reedrosenbluth force-pushed the feat/compute-cost-multiple-inputs branch from 6643167 to 398a500 Compare December 12, 2020 18:55
Copy link
Contributor

@kantai kantai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Member

@jcnelson jcnelson left a 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?

@reedrosenbluth
Copy link
Contributor Author

reedrosenbluth commented Dec 14, 2020

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?

https://github.com/blockstack/stacks-blockchain/blob/0261f0a401414e67eb5519d1ff0354d661ba8501/src/vm/costs/mod.rs#L760

@jcnelson jcnelson self-requested a review December 15, 2020 02:40
Copy link
Member

@jcnelson jcnelson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@reedrosenbluth reedrosenbluth merged commit 3617ac1 into feat/cost-contract-integration Dec 15, 2020
@blockstack-devops
Copy link
Contributor

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.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Nov 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants