index: organize Index and IndexStore errors into enums #7799
+58
−68
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.
Ahead of subsequent changes to convert more methods on
Index
,MutableIndex
,ReadonlyIndex
, andChangeIdIndex
to be fallible, these four changes:Index
andIndexStore
's disparate error types intoenum
s like other storage traits (e.g.BackendError
,OpStoreError
).IndexResult
type alias (like those ofBackendResult
andOpStoreResult
) that will help as more index trait methods are made fallible. We introduceIndexStoreResult
while we're at it, for symmetry with the other storage trait result types.By making
IndexError
anenum
and returning that fromIndex::all_heads_for_gc
, we allow for network-based implementations of this method to produce arbitrary I/O errors in addition to the existing case ofAllHeadsForGcUnsupported
.Let me know if there's anything I should change -- e.g. drop the
IndexStoreResult
alias, submit one PR per change, etc.Thanks!
Brian
Checklist
If applicable:
CHANGELOG.md
README.md
,docs/
,demos/
)cli/src/config-schema.json
)