Hi Simon,
On Tue, Sep 13, 2011 at 12:13 AM, Simon Michael wrote:
> Is that because of &= auto ?
I'm not sure. The feature was added in version 0.2 and is described in
issue 333:
http://code.google.com/p/ndmitchell/issues/detail?id=333
The description does not mention &= auto.
Sebastian
_
Please help make the regex-based parsing library efficient!
https://github.com/feuerbach/regex-applicative/wiki/Call-For-Help
--
Roman I. Cheplyaka :: http://ro-che.info/
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/ma
On 13 September 2011 14:08, Vasili I. Galchin wrote:
> Hello,
>
> I am trying to model multigraphs but getting errors with ghci and
> can't figure out why I have a serious blind spot
>
>
> {-# LANGUAGE MultiParamTypeClasses, FunctionalDependencies #-}
>
> module Bonzo where
>
>
Mystery solved.
The OpenCLRaw bindings were set to use ccall but OpenCL uses stdcall.
I've updated my branch of the bindings. Details on stackoverflow:
http://stackoverflow.com/questions/7391634/cant-link-opencl-on-windows-with-ghc
Jason
On Mon, Sep 12, 2011 at 10:29 AM, Jason Dagit wrote:
> H
Hello,
I am trying to model multigraphs but getting errors with ghci and
can't figure out why I have a serious blind spot
{-# LANGUAGE MultiParamTypeClasses, FunctionalDependencies #-}
module Bonzo where
class Graph arrow node where
source :: arrow -> node
Replying to someone's compliant in the first section:
Malcolm Wallace and Colin Runciman's ICFP99 paper functioned well as a
tutorial for HaXml when I used it - maybe it is a bit out of date now?
HaXml is hardly a dire case.
___
Haskell-Cafe mailing lis
Hello all,
I did a followup analysis of the free-form responses to "What is Haskell's
most glaring weakness / blind spot / problem" in the State of Haskell 2011
Survey. The article is up at:
http://nickknowlson.com/blog/2011/09/12/haskell-survey-categorized-weaknesses/
I think it has a lot of int
Hello,
I'm trying to get the OpenCLRaw bindings to a point where I can use
them on windows. I've forked the the OpenCLRaw repo on github so I
can make modifications as needed. My branch is here:
https://github.com/dagit/OpenCLRaw
I've been mostly working out of my "FunPtr" branch.
The issue I'
Thanks, i can check the ghc version on cabal file.
On Fri, Sep 9, 2011 at 6:53 PM, Joachim Breitner
wrote:
> Hi,
>
> Am Freitag, den 09.09.2011, 13:02 +0200 schrieb Luis Cabellos:
> >
> >I search the Haskell Platform webpage for older releases, I found
> > it but maybe it's worth to put a tab
Hi Sebastian,
On Sep 12, 2011, at 4:24 AM, Sebastian Fischer wrote:
>https://github.com/sebfisch/haskell-barchart/blob/v0.1.1.1/src/barchart.hs
>
> for an example of different modes that share most but not all of their
> options. IIRC, it works because in the list of exec modes later items
>
On 12 September 2011 23:29, Ryan Newton wrote:
> On Sun, Sep 11, 2011 at 1:14 PM, wren ng thornton wrote:
>>
>> On 9/11/11 6:37 AM, Neil Mitchell wrote:
>>>
>>> Why not email the maintainers of packages you think need a better
>>> description - ideally giving suggestions? I'd welcome that for any
On Sun, Sep 11, 2011 at 1:14 PM, wren ng thornton wrote:
> On 9/11/11 6:37 AM, Neil Mitchell wrote:
>
>> Why not email the maintainers of packages you think need a better
>> description - ideally giving suggestions? I'd welcome that for any of
>> my packages.
>>
>
> +1.
>
>
+1
Actually this thre
Hi Simon,
while it is not possible to reuse the definitions of common fields
themselves, their *descriptions* need to be given only once. Not sure
if you are already sharing descriptions or if it helps you saving a
few more lines. See
https://github.com/sebfisch/haskell-barchart/blob/v0.1.1.1
2011/9/12 Brandon Allbery :
> Don't all infix constructors have to start with a colon?
Yes that is true. You can of course use Unicode symbols as infix type variables:
(⋙) :: Category ⇝ => (α ⇝ β) -> (β ⇝ γ) -> α ⇝ γ
But a constructor must always begin with a capital letter or with a colon.
Uni
2011/9/12 Grigory Sarnitskiy
> Still
>
> {-# LANGUAGE TypeOperators #-}
> {-# LANGUAGE UnicodeSyntax #-}
>
> data a ── b = Foo a b
>
> leads to
>
> test.hs:4:6: Malformed head of type or class declaration: a ── b
> Failed, modules loaded: none.
>
Don't all infix constructors have to start with a
Still
{-# LANGUAGE TypeOperators #-}
{-# LANGUAGE UnicodeSyntax #-}
data a ── b = Foo a b
leads to
test.hs:4:6: Malformed head of type or class declaration: a ── b
Failed, modules loaded: none.
12.09.2011, 11:56, "Maciej Marcin Piechotka" :
> On Mon, 2011-09-12 at 11:51 +0400, Grigory Sarnitsk
On Mon, 2011-09-12 at 11:51 +0400, Grigory Sarnitskiy wrote:
> I want to have Unicode symbols for type operator:
>
> {-# LANGUAGE TypeOperators #-}
Add also:
{-# LANGUAGE UnicodeSyntax #-}
>
> data a ── b = Foo a b
>
> But it doesn't work. Any suggestions?
Regards
signature.asc
Description
I want to have Unicode symbols for type operator:
{-# LANGUAGE TypeOperators #-}
data a ── b = Foo a b
But it doesn't work. Any suggestions?
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
18 matches
Mail list logo
