<div dir="ltr">I think Henning has a point regarding defining:<div><br></div><div><font face="courier new, monospace"> o = fromString</font></div><div><br></div><div>All these libraries that Edward mentions already ask the user to paste a lot of boilerplate at the top of their module consisting of various extensions and imports. Why not simply remove the `OverloadedString`s pragma from the boilerplate and replace it with `o = fromString` and get almost the exact same benefits?</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 26, 2013 at 10:10 AM, Henning Thielemann <span dir="ltr"><<a href="mailto:schlepptop@henning-thielemann.de" target="_blank">schlepptop@henning-thielemann.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Am <a href="tel:26.08.2013%2019" value="+12608201319" target="_blank">26.08.2013 19</a>:03, schrieb Gabriel Gonzalez:<div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
May I propose an alternative solution? Why not just add a syntactic way<br>
to selectively opt in or out of `OverloadedStrings` for certain string<br>
literals? It could be something as simple as Python's trick for<br>
prefixing string literals with a single character to either enable or<br>
disable the overloading:<br>
<br>
example1 :: Int<br>
example1 = length "Non-overloaded string"<br>
<br>
example2 :: Parser Int<br>
example2 = o"Overloaded string" *> pure 4<br>
<br>
... but it doesn't have to be that specific solution. All that really<br>
matters is that it is syntactically lightweight.<br>
</blockquote>
<br></div>
This "opting in" already exists: Just put a space between o and the quotation mark and define "o = fromString". It's Haskell 98.<br>
<br>
I would prefer that solution to all syntactic extension experiments.<br>
<br>
</blockquote></div><br></div>