Opened 12 months ago

Last modified 10 months ago

#16282 new bug

all-missed-specializations doesn't suggest warning

Reported by: crockeea Owned by:
Priority: low Milestone:
Component: Compiler Version: 8.6.3
Keywords: newcomer Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Poor/confusing error message Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:


-Weverything turns on -Wall-missed-specializations. When most warnings print, they say, e.g.,

warning: [-Wincomplete-uni-patterns]

which is helpful because I can then easily suppress all warnings of that type with an -fno-warn-*. But missed specializations do not show the warning flag:

Foo.hs: warning:
    Could not specialise imported function `foo'
    Probable fix: add INLINABLE pragma on `foo'

There is no indication of what warning flag triggered the warning.

Change History (4)

comment:1 Changed 12 months ago by simonpj

There is no indication of what warning flag triggered the warning.

Good point. Ought to be easy to fix, if someone feels like doing it.

comment:2 Changed 12 months ago by RyanGlScott

Keywords: newcomer added

comment:3 Changed 12 months ago by crockeea

Differential Rev(s):

comment:4 Changed 10 months ago by Ben Gamari <ben@…>

In 3a38ea4/ghc:

Fix #16282.

Previously, -W(all-)missed-specs was created with 'NoReason',
so no information about the flag was printed along with the warning.
Now, -Wall-missed-specs is listed as the Reason if it was set,
otherwise -Wmissed-specs is listed as the reason.
Note: See TracTickets for help on using tickets.