On Tue, Oct 23, 2012 at 5:53 AM, Myles C. Maxfield <span dir="ltr">&lt;<a href="mailto:myles.maxfield@gmail.com" target="_blank">myles.maxfield@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>I am the author/maintainer of the &#39;punycode&#39; hackage package. After 4 months, I just found that punycode conversion already exists in the Data.Encoding.BootString package inside the &#39;encoding&#39; package. I&#39;d like to deprecate my package in favor of the &#39;encoding&#39; package.</div>


<div></div></blockquote></div><br><div>Please don&#39;t plan to do that. The encoding package may have filled a gap at some point, but now it looks old, unwieldy, inefficient (String), and weird (implicit parameters?) to me, and it&#39;s mostly obsolete (the standard I/O library has supported Unicode and encodings for a while now). I would not use the encodings package myself, for instance.</div>
<div><br></div><div>Your punycode package, in contrast, has a simple API and looks easy to use. I&#39;d suggest that you supprt the Text type as well as String, but otherwise please keep it around and maintain it.</div>