ndmitchell / ndmitchell/hoogle

Type constructor names should be case insensitive

Open
#128 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

From https://code.google.com/p/ndmitchell/issues/detail?id=415

Searching for DateTime -> Double should be the same as searching for Datetime -> Double, i.e. type constructor names should be insensitive.

As a side effect, searching for DOUBLE should just search for Double, not suggest that you might have meant Double (as it does now).

Additional examples abound, so this would be quite nice to fix.

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

Use the DateTime/Datetime and DOUBLE examples in the issue as the expected behavior, then locate the Hoogle search entry point that parses type constructor names and produces suggestions. Verify that differently cased constructor queries return the same results and that DOUBLE no longer produces a redundant suggestion.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
search
Issue type
Bug
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.