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
Yes, and the problem is what multiline comments handling is smth what can take much longer execution time, so i think i will check and maybe i can implement optional support for this.
I think a good solution (at least for me :D) would be setting a regex (preferably specific for a file type) which, if matched, causes the result to be dropped.
For example: I setup the regex ^[\t ]*\* for c++ files and any match (from my original comment that would be * This function wraps foo()) for a function definition which also matches the regex will be excluded from the list of definitions. It would be a good idea to keep them in the list of references, though.
This is purely from a user perspective, though. I have no idea how this would impact performance.
Say we have a function foo(). Somewhere in the codebase (e.g. some_file.cpp) a multi-line comment references it:
And when I try to find the definition for foo() I see
some_file.cpp:42 * This function wraps foo()
listed. Obviously this is undesired.The text was updated successfully, but these errors were encountered: