-
Notifications
You must be signed in to change notification settings - Fork 8
fix update.path nil pointer #360
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
Conversation
hansthienpondt
left a comment
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.
LGTM, deviation testing are failing because of known issue.
| name string | ||
| // updates is nil if the intent did not exist. | ||
| updates treetypes.UpdateSlice | ||
| updates []*treetypes.PathAndUpdate |
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.
is there a specific reason why we use a pointer type in the slice? There is not much performance gain and it risks more nil pointer issues in the future
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.
Habit I guess... but you're right it contains just pointers so lets make store the values.
alexandernorth
left a comment
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.
LGTM - we plan to discuss code style (pointers in slices vs not) later
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
No description provided.