ndmitchell / ndmitchell/hoogle
status of: "type search doesn't work" ?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 803
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
The landing page https://hoogle.haskell.org/ says "Warning: Alpha version, type search doesn't work!"
Indeed, e.g., Bool -> Bool gives different results (&& and id are missing)
(https://hoogle.haskell.org/?hoogle=Bool+-%3E+Bool vs https://www.haskell.org/hoogle/?hoogle=Bool+-%3E+Bool )
So I will recommend the "earlier hoogle" (which knows about partially applied functions,
and instantiating type parameters) to my students.
What is the status - what needs to be done to move these features to hoogle5? How hard would it be (does it require extra research or design, or ist "just coding")? Or is there a reason for not wanting it?
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 comparing the Hoogle 5 and earlier Hoogle results for the linked Bool -> Bool query, then investigate how type search handles partially applied functions and instantiated type parameters. The scope is to determine the required design or implementation work; done would mean the intended type-search behavior is restored or the remaining limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100