-
Notifications
You must be signed in to change notification settings - Fork 97
Deduplicate queryCurrentEraExpr calls #2104
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
Open
locallycompact
wants to merge
2
commits into
master
Choose a base branch
from
lc/query-deduplication
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
IMO the continuation passing is less clear than the
assumeShelleyBasedEraOrThrow
.Furthermore, the new code does a worse job in saying that it throws if the current era is not a shelley based era.
At the very least we should improve the name and/or add documentation about that to
queryForCurrentEraInShelleyBasedEraExpr
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 should have mentioned that I did this to prepare for the loss of
UTxO.fromApi
when porting to the upstreamCardano.Api.UTxO
, where we do not use a new type but only a newViewPattern
, and where we need to unify the ConwayEra witness for UTxO queries.https://github.com/cardano-scaling/hydra/pull/2061/files#diff-276e1103e4ea3e18432d556cad69781c3436da9f4026132b76cb74ae84c72504R219-R224
I don't know that this could have been done differently but this what I ended up with.
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.
Also the name is
queryForEraIn${EON}Expr
whereShelleyBasedEra
andConwaEraOnwards
are the literal Eon names.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.
Actually my opinion might be to push this somewhere where we can leave out the Era assumption and just unify it later, if it works.
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.
The reason why we query the current era from the node here (and similar functions in this module) is to make the request work across eras.
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.
Coercing to Era strikes me as a lie then in that case.