Why not propose adding a variant that exposes the error handling. Deprecation is a heavy hammer when most users seem to know that it&#39;s partial or discover it rather quickly. <span></span><br><br>On Thursday, August 18, 2016, Niklas Hambüchen &lt;<a href="mailto:mail@nh2.me">mail@nh2.me</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">My idea was to use DEPRECATED to indicate that it comes from a time<br>
where partial functions were considered OK, but this is no longer common<br>
practice now.<br>
<br>
WARNING would work just as well though, I&#39;d have no preference between<br>
the two.<br>
<br>
On 18/08/16 23:13, <a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;evan@evan-borden.com&#39;)">evan@evan-borden.com</a> wrote:<br>
&gt; If the intent is to keep this function indefinitely then why abuse<br>
&gt; DEPRECATED? Why not utilize WARNING?<br>
&gt;<br>
&gt; On Thu, Aug 18, 2016 at 7:50 AM, Oleg Grenrus &lt;<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;oleg.grenrus@iki.fi&#39;)">oleg.grenrus@iki.fi</a><br>
&gt; &lt;mailto:<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;oleg.grenrus@iki.fi&#39;)">oleg.grenrus@iki.fi</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;     So (as also pointed by Edward):<br>
&gt;<br>
&gt;     - Some people are aware that decodeUtf8 is partial and rely on that<br>
&gt;     behaviour<br>
&gt;     - Some people aren’t aware, and think that decodeUtf8 is like<br>
&gt;     `decodeUtf8With lenientDecode` or `decodeUtf8With ignore`.<br>
&gt;<br>
&gt;     Then if we add a {-# DEPRECATED #-} warning on `decodeUtf8`, we<br>
&gt;     should add variants for both use cases<br>
&gt;<br>
&gt;     lenientDecodeUtf8 which is total, and<br>
&gt;     unsafeDecodeUtf8 or strictDecodeUtf8, which is what decodeUtf8 does<br>
&gt;     today.<br>
&gt;<br>
&gt;     I’d like the new names, for convenience, `OnDecodeError` values<br>
&gt;     would require a new module import.<br>
&gt;<br>
&gt;     - Oleg<br>
&gt;<br>
&gt;<br>
&gt;     &gt; On 18 Aug 2016, at 14:40, Niklas Hambüchen &lt;<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;mail@nh2.me&#39;)">mail@nh2.me</a><br>
&gt;     &lt;mailto:<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;mail@nh2.me&#39;)">mail@nh2.me</a>&gt;&gt; wrote:<br>
&gt;     &gt;<br>
&gt;     &gt; On 18/08/16 18:11, Oleg Grenrus wrote:<br>
&gt;     &gt;&gt; Or should it be changed<br>
&gt;     &gt;&gt;<br>
&gt;     &gt;&gt; - decodeUtf8 = decodeUtf8With strictDecode<br>
&gt;     &gt;&gt; + decodeUtf8 = decodeUtf8With lenientDecode<br>
&gt;     &gt;<br>
&gt;     &gt; I&#39;d be very upset for that kind of a semantics change to sneak in<br>
&gt;     under me.<br>
&gt;     &gt;<br>
&gt;<br>
&gt;<br>
&gt;     ______________________________<wbr>_________________<br>
&gt;     Libraries mailing list<br>
&gt;     <a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;Libraries@haskell.org&#39;)">Libraries@haskell.org</a> &lt;mailto:<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;Libraries@haskell.org&#39;)">Libraries@haskell.org</a>&gt;<br>
&gt;     <a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries" target="_blank">http://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/libraries</a><br>
&gt;     &lt;<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries" target="_blank">http://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/libraries</a><wbr>&gt;<br>
&gt;<br>
&gt;<br>
______________________________<wbr>_________________<br>
Libraries mailing list<br>
<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;Libraries@haskell.org&#39;)">Libraries@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries" target="_blank">http://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/libraries</a><br>
</blockquote>