-
Notifications
You must be signed in to change notification settings - Fork 130
Gesture data structures #218
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
No more overriding operator& or providing implicit conversion. It's also now properly in a namespace, and uses traits classes to determine the underlying value type as well as the "invalid/empty" sentinel value.
Includes some basic tests.
Some modifications on rebase.
|
Added the unit tests on registered string map and correlated map as well. Tests are passing |
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.
Can just use constructor, safer and easier.
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.
Also, I'd move this fixture down to just before the tests that use it.
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.
Ok, using constructor now and moved fixture down before tests.
|
Can merge once the few changes are done. |
…tUp function, remove unused lines, use _eq not _streq for c++ str
|
Modified the tests according to comments above, ready for merge now |
These were pulled out of the massive gesture pull request and subsequent modifications. They seem to be reasonable now, still need unit tests for the registered string map. @mars979 ?