Opened 4 years ago
Closed 4 years ago
#10142 closed bug (fixed)
Documentation for Ix is contradictory around minimal definition
Reported by: | goldfire | Owned by: | hvr |
---|---|---|---|
Priority: | normal | Milestone: | 7.10.1 |
Component: | Core Libraries | Version: | 7.8.4 |
Keywords: | Cc: | core-libraries-committee@… | |
Operating System: | Unknown/Multiple | Architecture: | Unknown/Multiple |
Type of failure: | None/Unknown | Test Case: | |
Blocked By: | Blocking: | ||
Related Tickets: | Differential Rev(s): | Phab:D709 | |
Wiki Page: |
Description
The Haddock documentation for Ix
here says that the minimal definition requires range
, index
, and inRange
. But then it says that the minimal definition requires range
and inRange
. It seems that Haddock is inferring a MINIMAL
definition where none is in the code. Perhaps a MINIMAL
should be added.
Change History (5)
comment:1 Changed 4 years ago by
Owner: | changed from ekmett to hvr |
---|
comment:2 Changed 4 years ago by
Differential Rev(s): | → Phab:D709 |
---|---|
Status: | new → patch |
comment:3 Changed 4 years ago by
Milestone: | → 7.10.1 |
---|
comment:5 Changed 4 years ago by
Resolution: | → fixed |
---|---|
Status: | patch → closed |
landed to ghc-7.10 via 0d586136ce995f725bcaae064c98298d391ba178
Note: See
TracTickets for help on using
tickets.
so while
range
andinRange
have no default implementation,index
has one that is recursive:So the minimal pragma should specify that we minimally need
I'll make a patch rightaway...