Skip to content

Hackage search "compiler" misses purescript #474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
0joshuaolson1 opened this issue Jan 27, 2016 · 3 comments · Fixed by #632
Closed

Hackage search "compiler" misses purescript #474

0joshuaolson1 opened this issue Jan 27, 2016 · 3 comments · Fixed by #632
Assignees

Comments

@0joshuaolson1
Copy link

The "purescript" package has the word "Compiler" in its name, yet searching with neither the uppercase nor the lowercase word returns it among the results.

@gbaz
Copy link
Contributor

gbaz commented Feb 23, 2016

nice bug, searching for the word 'Compile' does seem to work. Perhaps an issue with the stemmer?

@mpickering
Copy link
Contributor

So the issue here from what I can work out is that a lot of packages mention the word "compiler" in the synopsis and description. This gets stemmed to "compil" so when pruneRelevantResults considers which search terms to include (from either ["compiler", "compil"]) it includes compiler as there are only 7 packages which include that term but there are more than 400 packages which include "compil" so this term isn't included. Maybe increasing the hard limit wouldn't be too bad but I can't really comment about the impact.

@gbaz
Copy link
Contributor

gbaz commented Sep 30, 2017

Doubling the soft and hard limit both I guess, as the limits should probably scale a bit with the overall size of hackage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants