Order by core libs first in search results #327
Comments
|
Perhaps it would be better to use number of reverse dependencies, i.e. a search result gets a small boost if it appears in a package which has more reverse dependencies (see also #292); that should achieve what's wanted here but also be useful for results outside of the core libraries. |
hdgarrood
added a commit
that referenced
this issue
Dec 25, 2017
Packages with more reverse dependencies are inserted into the trie earlier, which means that they appear earlier in the search results. This change means, for example, that the query "map" turns up the "map" from Prelude as the very first result. Fixes #327
hdgarrood
added a commit
that referenced
this issue
Dec 25, 2017
Packages with more reverse dependencies are inserted into the trie earlier, which means that they appear earlier in the search results. This change means, for example, that the query "map" turns up the "map" from Prelude as the very first result. Fixes #327
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mentioned here it'd be nice if names from core libs were displayed at the top, for example searching for apply, the definition of
<*>isn't shown until the fourth listing.The text was updated successfully, but these errors were encountered: