Re: aeson and dlist in HP 2013.4.0.0

2013-11-28 Thread Roman Cheplyaka
* Christian Maeder [2013-11-28 10:24:49+0100] > and attoparsec raises the question about how two different parser > packages should coexist in the HP I must have missed that — what is the question, exactly? Roman signature.asc Description: Digital signature

Re: aeson and dlist in HP 2013.4.0.0

2013-11-28 Thread Sven Panne
Just two add my 2c: Given all these new packages which would need to be pulled into the HP just for aeson, let's not include aeson for 2013.4.0.0 and release 2013.4.0.0 soon without the need for lengthy discussions. One of the main points of the HP is stability, and doing things in a useless rush n

Re: aeson and dlist in HP 2013.4.0.0

2013-11-28 Thread Sean Leather
On Wed, Nov 27, 2013 at 9:28 PM, Mark Lentczner wrote: > Okay - to put a concrete proposal on this: > > 1) Include dlist-0.6, which would have the additions that Sean L. has > proposed > [...] > ​*Sean* - do you have a time frame for such changes? > [...] dlist-0.6 is ready for imminent release.

Re: aeson and dlist in HP 2013.4.0.0

2013-11-28 Thread Roman Cheplyaka
* Christian Maeder [2013-11-28 12:27:30+0100] > Am 28.11.2013 11:40, schrieb Roman Cheplyaka: > >* Christian Maeder [2013-11-28 10:24:49+0100] > >>and attoparsec raises the question about how two different parser > >>packages should coexist in the HP > > > >I must have missed that — what is the q

Re: aeson and dlist in HP 2013.4.0.0

2013-11-28 Thread Bas van Dijk
On 28 November 2013 13:42, Sven Panne wrote: > Just two add my 2c: Given all these new packages which would need to > be pulled into the HP just for aeson, let's not include aeson for > 2013.4.0.0 and release 2013.4.0.0 soon without the need for lengthy > discussions. As the proposer for inclusio