no-internal-module raises an error for namespaces with nested paths

[vmmitev]

Consider the following example:

namespace Example.Utils { }

with no-internal-module set to to true an error is thrown starting at the Utils fragment. This can be applied to an arbitrary number of nested namespace paths, each of which raises an error of its own. A possible workaround is to rework the code-block as:

namespace Example {
    namespace Utils { }
}

If this is the intended way to apply the option it seems to add unnecessary verbosity and nesting to code. If it's not, my best bet is that the module/namespace declaration node is split into 2 or more elements which are visited, the first of which passes the namespace check and the rest end up as the error.

[adidahiya]

fixed in v2.5.0-dev.5