You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RFC: what should we do for namespaces for const/enums? As we have a collision here, I prepended the FISHEYE_ prefix, but we don't have do it for all namespaces (e.g. cv::utils::logging::).
The reason will be displayed to describe this comment to others. Learn more.
What if use namespace_prefix_override solution like for the functions? Namespace is already appended to the function names, if it's not overridden by config. It's less hacky and more obvious.
@asmorkalov , do you want me to split this PR in 3 per the 3 points I mentioned ? 2 should be easy to merge, the Python script needs more review (though parts of it can easily be merged, like the double const generation)
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.
enums were not taken into account
Pull Request Readiness Checklist
See details at https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request