Why are potentially partial literals scarier than the fact that every value in the language could lead to an exception when forced?<div><br><br><div class="gmail_quote">On Tue, Apr 24, 2012 at 5:35 AM, Yitzchak Gale <span dir="ltr">&lt;<a href="mailto:gale@sefer.org">gale@sefer.org</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Markus Läll wrote:<br>
&gt; You do know, that you already *can* have safe Text and ByteString from<br>
&gt; an overloaded string literal.<br>
<br>
</div>Yes, the IsString instances for Text and ByteString are safe<br>
(I hope).<br>
<br>
But in order to use them, I have to turn on OverloadedStrings.<br>
That could cause other string literals in the same module<br>
to throw exceptions at run time.<br>
<br>
-Yitz<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Glasgow-haskell-users mailing list<br>
<a href="mailto:Glasgow-haskell-users@haskell.org">Glasgow-haskell-users@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/glasgow-haskell-users" target="_blank">http://www.haskell.org/mailman/listinfo/glasgow-haskell-users</a><br>
</div></div></blockquote></div><br></div>