-
Notifications
You must be signed in to change notification settings - Fork 157
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
hide CostModel constructor #2703
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lehins
approved these changes
Mar 25, 2022
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.
Some suggestions, but with respect to improving safety of the code this is great
eras/alonzo/test-suite/src/Test/Cardano/Ledger/Alonzo/Serialisation/Generators.hs
Outdated
Show resolved
Hide resolved
The CostModel constructor should have been hidden when the EvaluationContext was added to it, costModelParamsToCostModel is the appropriate smart constructor that everyone should use. The evaluation context is completely dependend on the cost model parameters.
JaredCorduan
force-pushed
the
jc/hide-cost-model-constructor
branch
from
March 25, 2022 20:43
4354289
to
60c1c9f
Compare
JaredCorduan
pushed a commit
that referenced
this pull request
Apr 18, 2022
In the Alonzo era, the map of languages to cost models was mistakenly encoded using an indefinite CBOR map (contrary to cannonical CBOR, as intended) when computing the script integrity hash. For this reason, PlutusV1 remains with this encoding. Future versions of Plutus, starting with PlutusV2 in the Babbage era, will use the intended definite length encoding. PR #2703 accidentally reversed this Alonzo bug, this commit restores it.
JaredCorduan
pushed a commit
that referenced
this pull request
Apr 18, 2022
In the Alonzo era, the map of languages to cost models was mistakenly encoded using an indefinite CBOR map (contrary to cannonical CBOR, as intended) when computing the script integrity hash. For this reason, PlutusV1 remains with this encoding. Future versions of Plutus, starting with PlutusV2 in the Babbage era, will use the intended definite length encoding. PR #2703 accidentally reversed this Alonzo bug, this commit restores it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
CostModel
constructor should have been hidden when theEvaluationContext
was added to it,costModelParamsToCostModel
is the appropriate smart constructor that everyone should use. The evaluationcontext is completely dependent on the cost model parameters.