<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Is there some kind of general rule for when base should absorb things. In the last several years, it's pulled in Data.Functor.Identity, Data.Functor.Compose, Eq1, Ord1, Bifunctor. Is there any kind set of criteria these had to meet to be pulled in?<br><br>Sent from my iPhone</div><div><br>On Oct 20, 2016, at 12:02 PM, Iavor Diatchki <<a href="mailto:iavor.diatchki@gmail.com">iavor.diatchki@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">I am against extending `base`, as the functionality is already available outside it---a smaller `base` is easier to maintain, and gives us more room to evolve and change things. If the `free` package is considered "too heavy" of a dependency, then perhaps that package should be split into multiple smaller packages that provide the required functionality.<div><br></div><div>-Iavor</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 18, 2016 at 8:34 AM, Andrew Martin <span dir="ltr"><<a href="mailto:andrew.thaddeus@gmail.com" target="_blank">andrew.thaddeus@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">The advantages I outlined were:<span class=""><div><pre style="white-space:pre-wrap;color:rgb(0,0,0)">The advantage this offers is that Free and Cofree would be able to
enjoy a greater number of typeclass instances provided libraries
across the ecosystem. As it stands, adding the somewhat heavy `free`
dependency is not a good choice for libraries like `aeson`,
`mustache`, and `hashable`. In the case of Fix, the ecosystem
currently lacks a canonical library that provides it
(recursion-schemes and data-fix both offer the same definition though,
and various tutorials all define it the same way). It could benefit
from the new instances as well.
</pre></div><div><br></div></span></div><div class="gmail_extra"><span class=""><br><div class="gmail_quote">On Mon, Oct 17, 2016 at 2:31 PM, John Wiegley <span dir="ltr"><<a href="mailto:johnw@newartisans.com" target="_blank">johnw@newartisans.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">>>>>> "AM" == Andrew Martin <<a href="mailto:andrew.thaddeus@gmail.com" target="_blank">andrew.thaddeus@gmail.com</a>> writes:<br>
<br>
AM> I would gladly help with any of the work that needs to be done to make<br>
AM> this happen. I believe that Fix and Free (and Cofree to a lesser extent)<br>
AM> have proved themselves over years of use in the ecosystem. I would<br>
AM> appreciate any feedback or thoughts that others have on this topic.<br>
<br>
What advantage is there to having them in base, rather than living in the<br>
'free' package as they do now?<br>
<span class="m_7865576955365507471HOEnZb"><font color="#888888"><br>
--<br>
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F<br>
<a href="http://newartisans.com" rel="noreferrer" target="_blank">http://newartisans.com</a> 60E1 46C4 BD1A 7AC1 4BA2<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></span><span class="HOEnZb"><font color="#888888">-- <br><div class="m_7865576955365507471gmail_signature" data-smartmail="gmail_signature">-Andrew Thaddeus Martin</div>
</font></span></div>
<br>______________________________<wbr>_________________<br>
Libraries mailing list<br>
<a href="mailto:Libraries@haskell.org">Libraries@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/libraries</a><br>
<br></blockquote></div><br></div>
</div></blockquote></body></html>