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.
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
feat: Split methods between
HugrMut
andHugrMutInternals
#441feat: Split methods between
HugrMut
andHugrMutInternals
#441Changes from 5 commits
65002d3
f06543d
5cbac2e
2eff599
f14907b
6f90316
87e8d89
99be6cc
cb242e3
2419c75
3ba5511
bc2beb6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 wonder about the utility of naming the single field within, but not too worried
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 prefer to use named fields when the order is not relevant (what does
x.0
mean?). But I have no strong opinion on this.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 there are multiple fields of the same type (e.g.
expected
andactual
) then very much agree that named fields is the way to go. But here I don't think the name adds anything beyond what the type says already, and I really can't think of much else (of any type) you could put in an InvalidNode... (a validity-reason, perhaps. So ok if you prefer it this way!)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 changed it into a tuple struct for consistency with the other errors.