2 ms·
The difference is that "Add" is not a term that many search engines will drop on the floor. When you get out of the range of plain ASCII strings, you're leaving
by fixermark 11y ago
The difference is that "Add" is not a term that many search engines will drop on the floor. When you get out of the range of plain ASCII strings, you're leaving the range of symbols you can assume your tool of choice will be indexing into search for you.
This is likely a short-term reality, but it's the current reality.
- pcwalton 11y agoHow many code indexing tools are in use that aren't grep/ack/ag (because you can grep for +) and don't do semantic analysis? I can't think of any. Visual Studio, DXR (what I've used), all documentation tools, etc. can all handle overloaded operators, and have been able to for years. (Hasn't Visual Studio been able to index overloaded operators for, like, at least a decade?)
- fixermark 11y agogithub.com
- pcwalton 11y agoThat's fair. Though I've always found GitHub's code search to be less than useful in general. I think it doesn't really make sense to not have overloading because GitHub doesn't support semantic indexing in 2015, especially since you can easily just not use GitHub for code search.
- 15155 11y agoGitHub search breaks on really simple things, too: - Queries <= 3 characters in length - Certain common characters are totally not supported in queries - quotes, etc. - Forks cannot be searched. I always just clone and use a proper search tool if I know what I am looking for is in a specific codebase.