[arch-haskell] [jgm at berkeley.edu: Re: Pandoc restriction for Parsec <3]
magnus at therning.org
Sat Oct 12 07:36:12 UTC 2013
On Tue, Feb 16, 2010 at 19:13, Don Stewart <dons at galois.com> wrote:
>> On 16/02/10 01:09, Don Stewart wrote:
>> > The main user of parsec -- pandoc -- is *not* going to move to parsec 3,
>> > since it is twice as slow.
>> > That means that neither is the Haskell Platform
>> > That means that we should downgrade to parsec 2 on arch and *not move to
>> > parsec 3 for the foreseeable future*.
>> Is there any plan to still provide parsec 3 in Arch?
> I think if we can convince vegai to move haskell-parsec to parsec 2,
> then we can add special support for parsec 3.
> Then add support to cabal2arch to substitute.
That would be excellent.
Does anyone know if the speed issues in parsec 3 are inherent in the
algorithms used, or if a bit of profiling and optimisation will bring
it to par with parsec 2? (I'll take my answer in the form of a link
to a discussion on haskell-cafe if possible ;-)
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitter: magthe
More information about the arch-haskell