Skip to content
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

[Builtins] Drop 'RuntimeScheme' #4778

Merged
merged 20 commits into from
Aug 24, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update plutus-core/plutus-core/src/PlutusCore/Builtin/Meaning.hs
Co-authored-by: Michael Peyton Jones <michael.peyton-jones@iohk.io>
  • Loading branch information
effectfully and michaelpj authored Aug 16, 2022
commit 150c935405ac1c3abaf6d5caa97c5cf396bc1de1
2 changes: 1 addition & 1 deletion plutus-core/plutus-core/src/PlutusCore/Builtin/Meaning.hs
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ of the denotation and the costing function. This is because:

1. the two are fundamentally distinct and we have loads of documentation for each of them
separately, so conflating them in the actual API would be unnecessary coupling
2. right now it's clear which bits of the definition of a builtin consitute evaluation and which
2. right now it's clear which bits of the definition of a builtin constitute evaluation and which
ones constitute costing as the two are different arguments to 'makeBuiltinMeaning'. If evaluation
and costing were intertwined, it would be much harder to review the definition of a builtin
3. ... and it would also be more boilerplate and less clear type signatures
Expand Down