-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[Enhance] Update data structures #2155
[Enhance] Update data structures #2155
Conversation
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.
@Xiangxu-0103 Please fix the UT. Also, better to pull the latest code which has fixed some UTs and lints.
The updated |
Codecov ReportBase: 45.33% // Head: 45.51% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #2155 +/- ##
===========================================
+ Coverage 45.33% 45.51% +0.18%
===========================================
Files 255 255
Lines 21067 21095 +28
Branches 3325 3331 +6
===========================================
+ Hits 9550 9601 +51
+ Misses 10891 10868 -23
Partials 626 626
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
PointData
.BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist