May 2012 - Haskell-Cafe

ANN: meta-par, meta-par-accelerate and friends -- heterogeneous parallel programming
by Ryan Newton 05 May '12

05 May '12

Hi all, I'm happy to announce a release of meta-par, a parallel programming library that is a successor to monad-par. - http://hackage.haskell.org/package/abstract-par - http://hackage.haskell.org/package/monad-par - http://hackage.haskell.org/package/meta-par - http://hackage.haskell.org/package/abstract-par-accelerate - http://hackage.haskell.org/package/meta-par-accelerate The distributed programming components aren't released yet, but this blog posts describes how to use the above packages to do hybrid CPU/GPU programming: http://parfunk.blogspot.com/2012/05/how-to-write-hybrid-cpugpu-programs.html Cheers, -Ryan

1 0

conduit: Finalize field in PipeM
by Paolo Capriotti 05 May '12

05 May '12

Hi, I'm trying to write a function to convert a conduit to a Pipe (from pipes-core), and I'm having trouble understanding why the `Finalize` field in a `PipeM` constructor returns `r`. This makes it impossible to create it from the corresponding `M` constructor in pipes-core, since `M` includes an exception handler which is not guaranteed to run fully, hence may not provide a return value. `HaveOutput` presents a similar problem. >From a cursory look at conduit's code, it doesn't look like the return value of `Finalize` is ever used, and it seems that the conduits that actually manage to define it either have `()` as return type or just throw an exception. The definition of `lift` for the `MonadTrans` instance duplicates the base monad action there, which doesn't look quite right to me (isn't that supposed to contain a _cleanup_ action?). Shouldn't the constructor be changed to something like `PipeM (m (Pipe i o m r)) (Finalize m ())` or am I completely off base here? Thanks. BR, Paolo

2 2

Fwd: Problem with forall type in type declaration
by Chris Smith 04 May '12

04 May '12

Oops, forgot to reply-all again... ---------- Forwarded message ---------- From: Chris Smith <cdsmith(a)gmail.com> Date: Fri, May 4, 2012 at 8:46 AM Subject: Re: [Haskell-cafe] Problem with forall type in type declaration To: Magicloud Magiclouds <magicloud.magiclouds(a)gmail.com> On Fri, May 4, 2012 at 2:34 AM, Magicloud Magiclouds <magicloud.magiclouds(a)gmail.com> wrote: > Sorry, it was just a persudo code. This might be more clear: > > run :: (Monad m) => m IO a -> IO a Unfortunately, that's not more clear. For the constraint (Monad m) to hold, m must have the kind (* -> *), so then (m IO a) is meaningless. I assume you meant one of the following: run :: MonadTrans m => m IO a -> IO a or run :: MonadIO m => m a -> IO a (Note that MonadIO is the class from the mtl package; there is no space there). Can you clarify which was meant? Or perhaps you meant something else entirely? -- Chris Smith

1 0

Annoyed at System.Random
by Thomas DuBuisson 04 May '12

04 May '12

Ryan, I've grown annoyed at System.Random enough (specifically, StdGen). How much, if any, pushback would there be if I put together a FFI binding to a C AES-CTR based RNG. There are many advantages: 0) The API wouldn't have to change (though some parts should, and some change is already planned) 1) It can be fast (maybe not MT fast, but really quite good) 2) It's secure and the splitting properties can be related to cryptographic problems. 3) It could use Intel NI instructions when available. 4) It's NIST standardized, so there exist known answer tests. 5) We could expose a method to fill an arbitrary buffer :: Storable a => Ptr a -> Int -> IO () 6) The rest of the community doesn't have to do any of the work. I'd be tempted to pull in the 'entropy' package for seeding, but will make that a separate proposal. Cheers, Thomas

5 15

Indent aware parser
by Lyndon Maydwell 04 May '12

04 May '12

Hi all. What's the best indentation-aware parser at the moment? I see three when I look in cabal: lyndon@pugno:~ » cabal list indent * IndentParser Synopsis: Combinators for parsing indentation based syntatic structures Default available version: 0.2.1 Installed versions: [ Not installed ] Homepage: http://www.cse.iitk.ac.in/~ppk License: GPL * indentparser Synopsis: A parser for indentation based structures Default available version: 0.1 Installed versions: [ Not installed ] Homepage: http://www.cse.iitk.ac.in/users/ppk/code/HASKELL/indentparser License: PublicDomain * indents Synopsis: indentation sensitive parser-combinators for parsec Default available version: 0.3.2 Installed versions: [ Not installed ] Homepage: http://patch-tag.com/r/salazar/indents License: BSD3

2 2

unable to run ghci (7.4.1)?
by Baojun Wang 04 May '12

04 May '12

Dear list, I build haskell-platform 2011.04 by gentoo ~amd64 haskell overlay. But I can't run ghci even I rebuilt ghc or run haskell-updater, error message: ghci GHCi, version 7.4.1: http://www.haskell.org/ghc/ :? for help Loading package ghc-prim ... linking ... done. Loading package integer-gmp ... linking ... done. Loading package base ... linking ... ghc: /usr/lib64/ghc-7.4.1/base-4.5.0.0/HSbase-4.5.0.0.o: unknown symbol `stat' ghc: unable to load package `base' Do you have some ideas how to avoid this error? Many thanks. Best Regards Baojun

3 5

ANN: containers-0.5.0.0
by Johan Tibell 04 May '12

04 May '12

Hi all, I'm proud to announce a new major release of the containers package : http://hackage.haskell.org/package/containers-0.5.0.0 There has been a whopping 160 commits since the last release. The major improvements are: * a clearer distinction between value-lazy and value-strict containers, * performance improvements across the board, * a big internal clean-up, and * new functions for e.g. merging, updating, and searching containers. The first item is perhaps the most visible. While the old Data.Map and Data.IntMap modules will continue to exist for the foreseeable future, we've abandoned the practice of having the strict and lazy versions of each function distinguished by an apostrophe. The distinction is instead made at the module level, by introducing four new modules: * Data.Map.Strict * Data.Map.Lazy * Data.IntMap.Strict * Data.IntMap.Lazy This split has three benefits: * It makes the choice between value-strict and value-lazy containers more declarative; you pick once at import time, instead of having to remember to use the strict or lazy versions of a function every time you modify the container. * It alleviates a common source of performance issues, by forcing the user to think about the strictness properties upfront. For example, using insertWith instead of insertWith' is a common source of containers-related performance bugs. * There are fewer functions per module, making it easier to get an overview of each module. Note that the types used in the strict and lazy APIs are the same, so you can still use the same container in a "mixed" manner, if needed. Contributors to this release: Milan Straka Johan Tibell Joachim Breitner Edward Z. Yang Herbert Valerio Riedel Matt West Max Bolingbroke Cheers, The containers maintainers

1 0

Haskell source AST zipper with state
by Tony Morris 04 May '12

04 May '12

Is there a library to traverse a source AST keeping state? -- Tony Morris http://tmorris.net/

3 3

Tutorial on how to use multirec
by j.romildo＠gmail.com 04 May '12

04 May '12

Hello. I am writing a compiler in Haskell and need some tools to work with abstract syntax trees (like annotating them with source positions and other things). I have been pointed out to the multirec package. I have found some information about the package, but it is too dense to read and understand, as the ideas are presented from a theoretical point of view. So I am looking for something more light, as tutorials or simple applications that illustrate the use of the package. Any help? Romildo

1 0

Specify compile error
by Ismael Figueroa Palet 04 May '12

04 May '12

Hi, I'm writing a program like this: data B = B Int data A = Safe Int | Unsafe Int createB :: A -> B createB (Safe i) = B i createB (Unsafe i) = error "This is not allowed" Unfortunately, the situation when createB is called with an Unsafe value is only checked at runtime. If I omit the second case, it is not an error to not be exhaustive :-( Is there a way to make it a compile time error?? Thanks! -- Ismael

5 5