-
Notifications
You must be signed in to change notification settings - Fork 23
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
Haddocks for certain aspects of the HFC status quo #428
Draft
amesgen
wants to merge
5
commits into
main
Choose a base branch
from
amesgen/some-status-quo-hfc-docs
base: main
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.
Draft
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
32aef25
Init scriv for sop-extras and strict-sop-core
amesgen f87326f
Add `Ord (EraIndex xs)`
amesgen 6d9ac25
HFC: document that ticking alone can't reveal era transitions
amesgen b236a8a
Document requirements/usage of cross-era state translation
amesgen 6dd0b2b
Apply suggestions from code review
amesgen 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 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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,8 @@ | ||
# Revision history for sop-extras | ||
# sop-extras Changelog | ||
|
||
## 0.1.0.0 -- YYYY-mm-dd | ||
# Changelog entries | ||
|
||
<a id='changelog-0.1.0.0'></a> | ||
## 0.1.0.0 — 2023-09-07 | ||
|
||
* First version. Released on an unsuspecting world. |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
### Non-Breaking | ||
|
||
- Add `Ord (EraIndex xs)` instance |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
[scriv] | ||
format = md | ||
insert_marker = Changelog entries | ||
md_header_level = 2 | ||
version = literal: sop-extras.cabal: version | ||
categories = Patch, Non-Breaking, Breaking | ||
end_marker = scriv-end-here | ||
fragment_directory = changelog.d | ||
ghrel_template = {{body}} | ||
main_branches = master, main, develop | ||
new_fragment_template = file: new_fragment.${config:format}.j2 | ||
output_file = CHANGELOG.${config:format} | ||
skip_fragments = README.* |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,8 @@ | ||
# Revision history for strict-sop-core | ||
# strict-sop-core Changelog | ||
|
||
## 0.1.0.0 -- YYYY-mm-dd | ||
# Changelog entries | ||
|
||
<a id='changelog-0.1.0.0'></a> | ||
## 0.1.0.0 — 2023-09-07 | ||
|
||
* First version. Released on an unsuspecting world. |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
[scriv] | ||
format = md | ||
insert_marker = Changelog entries | ||
md_header_level = 2 | ||
version = literal: strict-sop-core.cabal: version | ||
categories = Patch, Non-Breaking, Breaking | ||
end_marker = scriv-end-here | ||
fragment_directory = changelog.d | ||
ghrel_template = {{body}} | ||
main_branches = master, main, develop | ||
new_fragment_template = file: new_fragment.${config:format}.j2 | ||
output_file = CHANGELOG.${config:format} | ||
skip_fragments = README.* |
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.
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 wording of this subheading seems off to me:
It seems like there are two things worth explaining/referencing:
The transition must have been predicted by
singleEraTransition
at least one safe zone before it happened.Ticking is currently unable to change the output of
singleEraTransition
.Right now, the text of this subheading could be interpreted as either of those two things. Is that ambiguity intentional?
Also, the text seems to call the first one a "reflection" of the second one, which I hesitate to agree 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.
This is what I wanted to talk about here in this subsection, but I didn't phrase it like this as you can't apply
singleEraTransition
to the output of ticking.I didn't intend to talk about safe zones here (but that could definitely happen in a different subsection, will add that 👍). In my mind, these two topics are orthogonal:
Yeah, I didn't want to imply that, hopefully, separating safe zones to its own section will make that more clear.