ndmitchell/hlint

`use camel case` emits *two* hints

Open

#1,529 opened on Jul 4, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Haskell (1,594 stars) (208 forks)batch import
good first issue

Description

Currently hlint emits two hints for something like

mk_meth_spec_prags :: ....
mk_meth_spec_prags = ...

both on the type and the method itself. I think it should only emit one hint.

Contributor guide

Tech stack
None
Domain
tooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Haskell syntax
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the Haskell source code for the 'Use camelCase' hint rule in hlint. The issue occurs when both a type signature and its corresponding value declaration trigger the hint. Examine the hint generation logic to ensure only one hint is emitted per pair. The relevant code is likely in the Hint module for naming conventions. Check any existing tests for this rule to understand expected behavior.