Ticket #1398 (closed feature request: fixed)

Opened 6 years ago

Last modified 4 years ago

-fno-monomorphism-restriction suggested when not appropriate

Reported by: iampure@… Owned by:
Priority: normal Milestone:
Component: GHCi Version: 6.6.1
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Difficulty: Easy (less than 1 hour)
Test Case: Blocked By:
Blocking: Related Tickets:

Description

Currently there are cases where -fno-monomorphism-restriction is suggested while the module already contains -fno-monomorphism-restriction in the OPTIONS_GHC option list. I have no ready made test case, although I am staring at one on my computer in version 6.6.1. I suggest checking whether fno-monomorphism-restriction was supplied and when it was do not recommend to add it.

Change History

Changed 6 years ago by simonpj

  • status changed from new to closed
  • resolution set to fixed

Good idea. Done.

Simon

Changed 6 years ago by Isaac Dupree

Hopefully it doesn't recommend -fno-monomorphism-restriction in those same cases if the flag *wasn't* passed to ghc (because it won't help...)

Changed 6 years ago by simonpj

I don't understand. All I've done is make sure you don't get a suggestion to do something you have already done. There is no claim that the suggestion will necessarily make things work even if you follow it!

S

Changed 5 years ago by simonmar

  • architecture changed from Unknown to Unknown/Multiple

Changed 5 years ago by simonmar

  • os changed from Unknown to Unknown/Multiple

Changed 4 years ago by simonmar

  • difficulty changed from Easy (1 hr) to Easy (less than 1 hour)
Note: See TracTickets for help on using tickets.