Okay, here's my current plan: I think I'm going to withdraw the ticket for
containers, and launch a package to be included in a future release of the
Haskell Platform.
First off, I'd like to know what the procedure is for adding something to
the Platform. I haven't been able to find a mailing
On 03/19/10 09:39, Louis Wasserman wrote:
Yo,
* I'm not comfortable with having two redundant modules, one for Min- and
one for MaxQueue
I'm pretty sure there won't be a containers-compatible solution, certainly
not a solution compatible with the style of containers as it's currently
Oh, god, so much to respond to...heh.
Submit this package for canonicalization as part of the Haskell Platform. I
would for one would support its inclusion.
This is an option I seriously hadn't considered. To be fair, that's because
I've never used the Platform myself, preferring rather to
On Thu, Mar 18, 2010 at 7:43 AM, Louis Wasserman
wasserman.lo...@gmail.com wrote:
Oh, god, so much to respond to...heh.
You did request feedback back there, didn't you :P
As does Python. In Python, though, the PQ implementation is not a built-in
class in the default namespace (as are dict and
Hi,
After about five hours' work (!!!) I *finally* managed to install Criterion
yesterday, so I'll send out those tests ASAP.
I wanted to use criterion too at one point, but it looked too hard to
install so I was scared away...
Why is that? Because of the Chart depencency?
You can
On Thu, Mar 18, 2010 at 4:43 PM, Louis Wasserman
wasserman.lo...@gmail.com wrote:
Submit this package for canonicalization as part of the Haskell Platform.
I would for one would support its inclusion.
This is an option I seriously hadn't considered. To be fair, that's because
I've never
Hi,
I don't like libraries getting bigger, I like them getting smaller.
When they're smaller they're easier to understand and easier to upgrade.
So I would also advice proposing your package for the HP (Haskell Platform).
I'm even for splitting containers into sub-packages: maps, sets,
First off: I've finally gotten set up with code.haskell.org. A darcs repo
of my binomial heap implementation is at
http://code.haskell.org/containers-pqueue/. Also on that site is the haddock
documentationhttp://code.haskell.org/containers-pqueue/containers-0.3.0.0/html/,
which I'm sure many
On Thu, Mar 18, 2010 at 10:39 PM, Milan Straka f...@ucw.cz wrote:
personally I am against splitting containers. It is a collection of
several basic data structures with similar design decisions
(reasonably efficient, can be used persistently, decent API).
I think these structures should stay
Hi,
On Thu, Mar 18, 2010 at 10:39 PM, Milan Straka f...@ucw.cz wrote:
personally I am against splitting containers. It is a collection of
several basic data structures with similar design decisions
(reasonably efficient, can be used persistently, decent API).
I think these structures
On 18 March 2010 22:02, Louis Wasserman wasserman.lo...@gmail.com wrote:
I'm still pretty strongly in favor of putting priority queues into
containers: other programming languages consider it necessary for inclusion
into standardized libraries, people will be more likely to use appropriate
Okay, let me ask the following question:
Would anybody besides me be heartbroken if priority queues *weren't* put
into containers, but were instead put into the Platform?
Louis Wasserman
wasserman.lo...@gmail.com
http://profiles.google.com/wasserman.louis
On Thu, Mar 18, 2010 at 6:50 PM,
On Mar 18, 2010, at 18:33 , Milan Straka wrote:
I would like to have basic data structures connected together. I do
not
really mind if the modules are in one library or in several, as long
as
I could say I want 'containers'.
This is what the Haskell Platform is for. No real need to add
On Mar 18, 2010, at 19:50 , Thomas Schilling wrote:
The Haskell Platform is really is intended to be available at your
fingertips. Unfortunately, the following does not work (although I
thought it's supposed to)
$ cabal install haskell-platform
Other way around: installing the Haskell
14 matches
Mail list logo
