If you insist on adding Proxy to Data.Typeable, I'd like to strongly suggest that we might want to look at promoting Data.Proxy from the tagged package to base.<div><br></div><div>It offers a lot of instances that I currently rely upon in production code and is already in use in a large portion of the ~42 reverse dependencies of that package:</div>
<div><br></div><div><a href="http://packdeps.haskellers.com/reverse/tagged">http://packdeps.haskellers.com/reverse/tagged</a></div><div><br></div><div>Of course we could invert the dependencies from packages outside of base at that time.<div>
<br></div><div>Exporting a crippled Proxy from Data.Typeable <i>without</i> those instances will basically just ensure that I need to somehow support both, fight needlessly with orphans and/or deal with qualified imports everywhere, and it will break about 3 dozen modules of mine, and impact others.</div>
<div><br></div><div>All in all this makes me personally rather strongly opposed to the idea of just randomly throwing a Proxy type in the module without ensuring we don't lose existing functionality along the way.</div>
<div><br></div><div><div>-Edward<br><br><div class="gmail_quote">On Wed, Mar 20, 2013 at 4:04 AM, José Pedro Magalhães <span dir="ltr"><<a href="mailto:jpm@cs.uu.nl" target="_blank">jpm@cs.uu.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Data.Typeable no longer uses Proxy, yet I think it is convenient to have a Proxy datatype<br>defined somewhere in base, and re-export it from Data.Typeable, as you might often often<br>
want to use it.<br><br><br>Cheers,<br>
Pedro<div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">On Wed, Mar 20, 2013 at 12:35 AM, Edward Kmett <span dir="ltr"><<a href="mailto:ekmett@gmail.com" target="_blank">ekmett@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+1 for finding a resolution. The idea of another Proxy floating around fills me with unease.<span><font color="#888888"><div><br></div></font></span><div><span><font color="#888888">-Edward<br>
<br></font></span><div class="gmail_quote"><div><div>On Tue, Mar 19, 2013 at 7:48 PM, Ben Gamari <span dir="ltr"><<a href="mailto:bgamari.foss@gmail.com" target="_blank">bgamari.foss@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div>José Pedro Magalhães <<a href="mailto:jpm@cs.uu.nl" target="_blank">jpm@cs.uu.nl</a>> writes:<br>
<br>
> Yes, it's entirely unproblematic, and a good suggestion.<br>
><br>
</div>What happened to this proposal? As far as I can tell the new-typeable<br>
work is in (or rather, the branch has been deleted) yet Data.Typeable<br>
still seems to have its own Proxy. Given that there has been talk of a<br>
7.8 release, this should probably be resolved quickly (although it's not<br>
clear to me from the massive thread where that discussion concluded).<br>
<br>
Cheers,<br>
<br>
- Ben<br>
</div></div><div><div><br><div>
_______________________________________________<br>
Libraries mailing list<br>
<a href="mailto:Libraries@haskell.org" target="_blank">Libraries@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
</div></div></div></blockquote></div><br></div>
</blockquote></div><br>
</div></div></blockquote></div><br></div></div></div>