purescript / purescript/pursuit
Build-in knowledge of some type synonyms / operators?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
For example, people might not know that the type of Data.Array.fromFoldable is forall f a. Foldable f => f ~> Array; this means that the query f a -> Array a does not pick it up. One way to address this could be to build in knowledge of some basic type operators like ~>.
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
The issue names no files, tests, or implementation entry point. Start by locating the type-query matching and operator handling for queries such as f a -> Array a, then determine how built-in knowledge of ~> or type synonyms should be specified and tested; done means the example query finds Data.Array.fromFoldable without regressing existing searches.
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