purescript / purescript/pursuit

Rank class members higher in search results

Open
#362 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haskell
Stars
174
Forks
47
PR merge metrics
No merged PRs in 30d

Description

The issue can be demonstrated using the example search of (a -> b) -> f a -> f b
The functions liftA1 and liftM1 get higher priority than map. Class members with the same signature as other functions are probably more useful/general than those other top-level functions.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No implementation file or test is named. Start by reproducing the (a -> b) -> f a -> f b search and inspect the search-ranking entry point to compare liftA1, liftM1, and map. Done means class members with matching signatures rank above less general top-level functions, with coverage for the example.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.