-
Notifications
You must be signed in to change notification settings - Fork 15
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 GOV from conformance #688
base: master
Are you sure you want to change the base?
Conversation
88d13eb
to
235bdaf
Compare
cd255b3
to
244bc92
Compare
5943b7b
to
5ecd7ea
Compare
f42bd3d
to
d822d14
Compare
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.
Looks good! Removing code is always great!
_⊢_⇀⦇_,GOV⦈_ = ReflexiveTransitiveClosureᵢ {sts = _⊢_⇀⦇_,GOV'⦈_} | ||
_⊢_⇀⦇_,GOV⦈_ : GovEnv → GovState → List (GovVote ⊎ GovProposal) → GovState → Type | ||
Γ ⊢ govSt ⇀⦇ gvps ,GOV⦈ govSt' | ||
= ⟦ txid , epoch , pparams , ppolicy , enactState , conv certState , rewardCreds ⟧ L.⊢ govSt |ᵒ conv certState ⇀⦇ gvps ,GOV⦈ govSt' |
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.
What's the reason you moved |ᵒ
here from LEDGER
?
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.
If we called |ᵒ in Ledger
then we would have to expose the conversion function as well. In this way, I think is more modular.
Description
Currently the GOV rules in Conformance are analogous (modulo
CertState
) to those in Ledger.This PR aims to remove the redundancy.
This PR consists of two commits:
Equivalence.Base
where needed. This serves to break cyclic dependencies which occur in the next commit.Ledger.Conway.Conformance.Gov
as an interface forLedger.Gov
.TBD
Checklist
CHANGELOG.md