x/pkgsite: standard library packages should be prioritized in search results

[jzacsh]

What is the URL of the page with the issue?

https://pkg.go.dev/search?q=net%2Fhttp+Request

What is your user agent?

chromeos (Mozilla/5.0 (X11; CrOS x86_64 13099.102.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.127 Safari/537.36)

Screenshot

What did you do?

searched http Request and net/http Request and both shows similar results not highlighting the std library.

What did you expect to see?

net/http package should have been a top result for both queries. for my exact query in particular, i was trying to land here: https://pkg.go.dev/net/http?tab=doc#Request

more generally maybe anything with a match in https://pkg.go.dev/std?tab=packages should be ranked higher?

What did you see instead?

only non-standard lib packages on the first page of results.

---

for the person that triages this report: I looked in https://github.com/golang/go/milestone/164 and didn't see this bug, but similar asks: #40785 #40622 #40311 (and #40311 one's perhaps a better, more general ask, but ... maybe not. std library feels particularly important regardless of how widely used it is).

[errhandler]

Searching for 'regex' doesn't even return the standard library 'regexp' package in the first 100 results.

[Deleplace]

I'm reporting #64358 for a specific subset of this problem.

[jba]

The problem is that you're searching for a package and a symbol, and we don't index packages on their symbols.

We shouldn't need (or want) to prioritize the standard library over other packages. We already take into account the number of importing packages. For popular stdlib packages like net/http, that will do the job. If a stdlib package is not as popular as some others, it should not be prioritized.

If you perform a symbol search for Request (enter #Request in the search box), then net/http will be at the top.

[mvdan]

@jba @seankhliao I'm sorry but #42129 and #40622 were both closed as duplicates of this one, now also closed, even though neither of the other issues searched for packages and symbols at the same time. They both just searched for a package name verbatim. Please reopen either this issue or the other two.

[mvdan]

Ah, I see now that you reopened #64358. We had a number of these, so I'll happily follow that one now.