-fno-monomorphism-restriction suggested when not appropriate
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.
Trac metadata
Trac field | Value |
---|---|
Version | 6.6.1 |
Type | FeatureRequest |
TypeOfFailure | OtherFailure |
Priority | normal |
Resolution | Unresolved |
Component | GHCi |
Test case | |
Differential revisions | |
BlockedBy | |
Related | |
Blocking | |
CC | |
Operating system | Unknown |
Architecture | Unknown |