Our V2 doesn't <i>quite</i> match, since V2 requires the two fields to have the same type, but I agree. =)<br><br><div class="gmail_quote">On Thu, Oct 18, 2012 at 2:36 PM, Anthony Cowley <span dir="ltr"><<a href="mailto:acowley@seas.upenn.edu" target="_blank">acowley@seas.upenn.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, Oct 18, 2012 at 4:47 PM, Ivan Lazar Miljenovic<br>
<<a href="mailto:ivan.miljenovic@gmail.com">ivan.miljenovic@gmail.com</a>> wrote:<br>
> On 19 October 2012 04:57, Henning Thielemann<br>
> <<a href="mailto:lemming@henning-thielemann.de">lemming@henning-thielemann.de</a>> wrote:<br>
>><br>
>> On Thu, 18 Oct 2012, Brent Yorgey wrote:<br>
>><br>
>>> I am +1 for this proposal, but only as long as these instances are not<br>
>>> exported by the Prelude. They are useful when you know you want them<br>
>>> but will confuse newbies -- based on evidence from #haskell, where<br>
>>> lambdabot has such instances in scope.<br>
>><br>
>><br>
>> Please no orphan instances - I think a pair type that supports arithmetics<br>
>> deserves a custom type.<br>
><br>
> Agreed. Another -1 on the proposal from me.<br>
<br>
</div>I am also with Henning, and a -1 for the proposal. If it's too<br>
confusing to export by default, then the instance belongs to a less<br>
general type. There are appropriate types that have the desired<br>
behavior all over hackage. I am currently partial to V2 from the<br>
linear package.<br>
<span class="HOEnZb"><font color="#888888"><br>
Anthony<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Libraries mailing list<br>
<a href="mailto:Libraries@haskell.org">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></blockquote></div><br>