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
In both cases Iterable::begin() returns an Iterator.
Yet, in the cppinsights output, the former iterator appears as Iterator instead of Iterable::Iterator. In the latter case, the leading MYNAMESPACE:: is printed correctly.
I think it would be nice if the leading Iterable:: would also be printed in the former case (for disambiguation, should someone run into a case where that's necessary), and such that the printout of cppinsights is valid code.
The text was updated successfully, but these errors were encountered:
comparing this and this example, there is a custom iterator class in both cases.
Abbreviated, in the former, the iterator definition is in another class
In the latter, the iterator is defined in some namespace
In both cases
Iterable::begin()
returns anIterator
.Yet, in the cppinsights output, the former iterator appears as
Iterator
instead ofIterable::Iterator
. In the latter case, the leadingMYNAMESPACE::
is printed correctly.I think it would be nice if the leading
Iterable::
would also be printed in the former case (for disambiguation, should someone run into a case where that's necessary), and such that the printout of cppinsights is valid code.The text was updated successfully, but these errors were encountered: