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.
I'm not a super huge fan of the
MutablePathMutableHandleGraph
. In practice this going to be one of our goto classes. Do we really need theMutable
specifier twice? Here's a proposal:MutablePathMutableHandleGraph
andMutablePathDeletableHandleGraph
MutablePathHandleGraph
now means the Graph and Path is mutableDeletablePathHandleGraph
which likewise had deletable paths and graphThis makes the header files less modular, but as discussed in #16, we probably don't want to move forward with cross-products of features.