From the Bitbucket Code Search Blog: Search indices built using traditional text indexers will usually return the usage result first because it contains a highe

From the Bitbucket Code Search Blog: Search indices built using traditional text indexers will usually return the usage result first because it contains a higher number of exact matches for your search term. In code bases where the same class or function is used many times, developers are often left trawling through page after page of usage results trying to hunt down the definition. Bitbucket took a different approach: by boosting the definitions matching your search term, the result you want is likely to rank much higher (usually #1) in the search results. Bitbucket's algorithm boosts definitions for a wide range of type categories including classes, functions, enums, structs, and interfaces. Bitbucket prioritized building a code aware search scoped to team and user accounts over a global search functionality. This way, we hope to quickly give users the relevant results they want instead of the hassle of checking out a repo locally and searching using an IDE. https://blog.bitbucket.org/2017/05/02/introducing-code-aware-search-for-bitbucket-cloud/ https://blog.bitbucket.org/2017/05/02/introducing-code-aware...