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 line is looking for template instantiations that are qualified with the scope resolution operator (::). The pattern matches instantiations with only a single operator (such as bar::Foo) but not those with multiple operators (such as baz::bar::Foo). I believe the correct pattern is ^\w*(::\w+)+<
The text was updated successfully, but these errors were encountered:
Is there a scenario you're encountering that makes this change necessary? Because we don't support nested namespaces (or classes) so there's not really a situation (we don't think) where this would come into play. Please provide examples if you are having a problem with how it is currently implemented that this change fixes.
TrickCAT uses lots of nested namespaces, which didn't cause any problems until f8a079e. #1753 restores enough support for nested namespaces to allow TrickCAT to build within Trick again. Consider it a small step on the path from "we don't support nested namespaces at all" to "we partially support nested namespaces."
This line is looking for template instantiations that are qualified with the scope resolution operator (
::
). The pattern matches instantiations with only a single operator (such asbar::Foo
) but not those with multiple operators (such asbaz::bar::Foo
). I believe the correct pattern is^\w*(::\w+)+<
The text was updated successfully, but these errors were encountered: