ndmitchell / ndmitchell/hoogle

Make Control.Arrow.first and second easier to find

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

Nobody has claimed this yet.

Dominant language
Haskell
Stars
803
Forks
152
PR merge metrics
No merged PRs in 30d

Description

Searching for (a->b) -> (c,a) -> (c,b) , i.e., "apply a function to the second part of a tuple" (IMHO a common operation), does not find Control.Arrow.second.

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

Start by reproducing the reported tuple-transformation query in Hoogle and checking how Control.Arrow.second is indexed and ranked. Done means this common query finds Control.Arrow.second, with the corresponding behavior covered by an appropriate test if the repository provides one.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
search
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.