No, if that answers your question, good. Ben: is this change in the release notes? Simon | -----Original Message----- | From: andres.sicard.ramirez@gmail.com | [mailto:andres.sicard.ramirez@gmail.com] On Behalf Of Andrés Sicard- | Ramírez | Sent: 21 January 2016 13:25 | To: Simon Peyton Jones <simonpj@microsoft.com> | Cc: Thomas Miedema <thomasmiedema@gmail.com> | Subject: Re: GHC 8.0.1 RC 1 and the -fwarn-monomorphism-restriction | option | | On 21 January 2016 at 08:11, Simon Peyton Jones | <simonpj@microsoft.com> wrote: | > Can you give a small concrete test case, showing the different | behaviour? | | I received this answer from Thomas Miedema: | | Thomas Miedema <thomasmiedema@gmail.com> wrote: | > Reinstate monomorphism-restriction warnings | > | > This patch is driven by Trac #10935, and reinstates the | > -fwarn-monomorphism-restriction warning. It was first lost in | 2010: | > d2ce0f52d "Super-monster patch implementing the new typechecker | -- at | > last" | > | > I think the existing documentation is accurate; it is not even | > turned on by -Wall. | > | > I added one test. | | It was exactly what I was looking for. Do you still need a concrete | test case? | | -- | Andrés