<br><br><div class="gmail_quote">On Thu, Nov 1, 2012 at 8:28 AM, Christian Maeder <span dir="ltr"><<a href="mailto:Christian.Maeder@dfki.de" target="_blank">Christian.Maeder@dfki.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Am 29.10.2012 10:05, schrieb José Pedro Magalhães:<br>
[...]<div><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It's been proposed to remove the possibility to derive Typeable or write<br>
instances for it.<br>
I'm supposing the way that this would be implemented would be:<br>
<br>
7.8: Any uses of "deriving Typeable" would give rise to a warning saying<br>
that it is no longer<br>
necessary. Any instances of Typeable would give rise to a warning saying<br>
that this code<br>
is being ignored, and replaced by an internal Typeable instance.<br>
Packages might break,<br>
or change runtime behaviour due to this change.<br>
<br>
7.10: Explicit uses of "deriving Typeable" or instances are an error.<br>
</blockquote>
<br></div>
I would vote against making "deriving Typeable" an error as this would break a lot of existing code (and is recommended by current deprecation warnings).<br>
<br>
Ignoring it (with or without warning) is the right thing to do (IMHO).<br>
<br>
Furthermore there's a language flag DerivingTypeable, that should be ignored, too, then.<br></blockquote><div><br>The flag is actually DeriveDataTypeable, and Data isn't changing, so that flag must stay<br>(or be renamed to DeriveData...)<br>
<br><br>
Cheers,<br>Pedro<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers Christian<br>
<br>
</blockquote></div><br>