ndmitchell / ndmitchell/hoogle
hoogle listing Prelude first?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 803
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
I thought earlier hoogle would list Prelude later (ie not as the first module hit) - or maybe something else is going on?
I haven't checked around carefully but I noticed several results listing Prelude as the first matching module.
So I am not sure if this is a regression or intended change of behaviour or simplification?
Not the end of the world for sure - but since the Prelude module is quite long preferring other modules would be better like earlier.
I should look at the code I suppose...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported Hoogle searches and inspect how result modules are ranked, with particular attention to why Prelude appears first. Compare the current ordering with the earlier behavior described in the issue; done means determining whether this is intentional or restoring the preferred ordering with a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100