-
Notifications
You must be signed in to change notification settings - Fork 184
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
UnicodeSet Builder L2 #195
Conversation
Pull Request Test Coverage Report for Build 0582acb9f2970b30bb1669aeb832094b1317df5a-PR-195
💛 - Coveralls |
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.
A few initial comments
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.
Great work!
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 think add
and remove
should be essentially the same algorithm, with just minor differences (e.g., switching even for odd). Can you make the two functions more similar to each other, for example, by making the variable names the same? If there are any differences in business logic, try to figure out why those differences exist and leave comments.
I still have an open comment, but otherwise this looks good. |
The L2 Builder API as discussed in #91.
Provides:
UnicodeSetBuilder::new()
UnicodeSetBuilder::build() -> UnicodeSet
add_char
,add_range
,add_set
remove_char
,remove_range
,remove_set
retain_char
,retain_range
,retain_set
complement
,complement_char
,complement_range
,complement_set