ere a inner implicit brace and a outer explicit brace is
closed at the same time
to be processed by the rule in Snippet 6,
but it doesn't work since Snippet 2 is before Snippet 6 in the
definition of L
and parse-error(t) is always false if t = '}'.
The fix of this problem is easy: replace Snippet 2 wi
race and a outer explicit brace is closed
at the same time
to be processed by the rule in Snippet 6,
but it doesn't work since Snippet 2 is before Snippet 6 in the definition
of L
and parse-error(t) is always false if t = '}'.
The fix of this problem is easy: replace Snippet 2 with Snippet 3.
T
---
src/Main.hs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/Main.hs b/src/Main.hs
index 828e55c..12d377f 100644
--- a/src/Main.hs
+++ b/src/Main.hs
@@ -101,7 +101,7 @@ cmdConvertDbOpts = CmdConvertDb
$ strOption (short 'i' long indb value cblrepo.db help old
Daniel Wagner wrote:
On 2013-07-18 10:46, harry wrote:
Why not let all types carry the dictionary automatically, or at least every
time that it's used, if that would incur a memory/performance penalty? GHC
tells me which context to add when it's missing, so it clearly knows.
I'm not sure the
Why not this?
data Pair = forall a. Eq a = Pair {x::a, y::a}
equal :: Pair - Bool
equal (Pair x y) = x == y
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Hm, also, with equality constraints you can make the type parametrized, too:
data Pair a' = forall a. (a ~ a', Eq a) = Pair {x::a, y::a}
equal :: Pair a - Bool
equal (Pair x y) = x == y
On 18 July 2013 13:00, Christopher Done chrisd...@gmail.com wrote:
Why not this?
data Pair = forall a. Eq
I'd use GADT syntax for this:
{-# LANGUAGE GADTs #-}
data Pair a where Pair :: Eq a = {x::a, y::a} - Pair a
Sjoerd
On Jul 18, 2013, at 1:05 PM, Christopher Done chrisd...@gmail.com wrote:
Hm, also, with equality constraints you can make the type parametrized, too:
data Pair a' = forall a.
Good point, classic use-case for GADTs.
On 18 July 2013 13:11, Sjoerd Visscher sjo...@w3future.com wrote:
I'd use GADT syntax for this:
{-# LANGUAGE GADTs #-}
data Pair a where Pair :: Eq a = {x::a, y::a} - Pair a
Sjoerd
On Jul 18, 2013, at 1:05 PM, Christopher Done chrisd...@gmail.com
.nabble.com/How-to-fix-DatatypeContexts-tp5733103p5733110.html
Sent from the Haskell - Glasgow-haskell-users mailing list archive at
Nabble.com.
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman
://haskell.1045720.n5.nabble.com/How-to-fix-DatatypeContexts-tp5733103p5733112.html
Sent from the Haskell - Glasgow-haskell-users mailing list archive at
Nabble.com.
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http
I've also been experiencing this a lot in class instances, such as:
class Foo f where
foo :: a - f a
data Bar f a = Foo f = Bar {bar :: f a}
instance Foo (Bar f) where
foo a = Bar (foo a)
Is there any way to avoid repeating the Foo f constraint in the Bar f
instance?
On Jul 18, 2013, at 2:35 PM, harry volderm...@hotmail.com wrote:
Sjoerd Visscher-2 wrote
equal pair@Pair{} = foo pair == bar pair
Interesting solution, I didn't know you could do that. (Do all those who
suggested GADTs - you can add a type context to the constructor of a regular
data type
that the
type system could be enhanced, so that the compiler understands that Bar f
= Foo f without being told so explicitly every time?
--
View this message in context:
http://haskell.1045720.n5.nabble.com/How-to-fix-DatatypeContexts-tp5733103p5733117.html
Sent from the Haskell - Glasgow-haskell
On Thu, Jul 18, 2013 at 9:58 AM, harry volderm...@hotmail.com wrote:
Which brings me back to my original question - is there any way that the
type system could be enhanced, so that the compiler understands that Bar
f
= Foo f without being told so explicitly every time?
No. The point is,
time that it's used, if that would incur a memory/performance penalty? GHC
tells me which context to add when it's missing, so it clearly knows.
--
View this message in context:
http://haskell.1045720.n5.nabble.com/How-to-fix-DatatypeContexts-tp5733103p5733119.html
Sent from the Haskell - Glasgow
On 2013-07-18 10:46, harry wrote:
Why not let all types carry the dictionary automatically, or at least
every
time that it's used, if that would incur a memory/performance penalty?
GHC
tells me which context to add when it's missing, so it clearly knows.
I'm not sure the claim in your second
(#8026) in this way was rejected as unsound, as
some nefarious uses of undefined would break the type system.
Is there any way that the type system could be enhanced to avoid this
redundancy?
--
View this message in context:
http://haskell.1045720.n5.nabble.com/How-to-fix-DatatypeContexts
I don't know how to express it. You need to have some dynamic
representation since
dag is a container of `(Int, f Int)`. I've tried to go along this road
type Exp a = Fix (E a)
data E c :: * - * where
Lit :: Show a = a - E a c
Op :: Op a - E a c
App :: Phantom (a - b) c - Phantom a c - E
On Tue, Feb 19, 2013 at 9:28 PM, Anton Kholomiov
anton.kholom...@gmail.comwrote:
Do you think the approach can be extended for non-regular (nested)
algebraic types (where the recursive data type is sometimes at a different
type instance)? For instance, it's very handy to use GADTs to capture
` constraint. A better representation might be typed ASGs [1]
Syntactic has typed ASTs and it has a module that does something similar
to data-fix-cse (uses a combination of stable names and hashing), but it
needs some fixing up.
/ Emil
[1]: http://dl.acm.org/citation.cfm?id=2426909
2013-02-20 01:58
of the references for
values
when `data-fix-cse` doesn't sacrifices the purity.
A short example:
Let's define a tiny DSL for signals
import Data.Fix
type Name = String
type E = Fix Exp
data Exp a = Const Double | ReadPort Name | Tfm Name [a] | Mix a a
deriving (Show, Eq, Ord)
We can make
instead of data-fix. Compdata has support for composable
types and lots of extra functionality. On the other hand, it's easy
enough to translate from compdata terms to your `Fix`...
One side-note form my experience: Fixpoint types can be very flexible.
It's easy to compose them. If suddenly we
class `Traversable`.
One way to make the library even more useful would have been to base it on
compdata instead of data-fix. Compdata has support for composable types and
lots of extra functionality. On the other hand, it's easy enough to
translate from compdata terms to your `Fix
as fixpoint type[2]. And
then all
you need
to use the library is to define the instance for type class
`Traversable`.
One way to make the library even more useful would have been to base
it on compdata instead of data-fix. Compdata has support for
composable
for
values
when `data-fix-cse` doesn't sacrifices the purity.
A short example:
Let's define a tiny DSL for signals
import Data.Fix
type Name = String
type E = Fix Exp
data Exp a = Const Double | ReadPort Name | Tfm Name [a] | Mix a a
deriving (Show, Eq, Ord)
We can make constant signals
Do you think the approach can be extended for non-regular (nested)
algebraic types (where the recursive data type is sometimes at a different
type instance)? For instance, it's very handy to use GADTs to capture
embedded language types in host language (Haskell) types, which leads to
#7486: dblatex can't build docs; fix included.
--+-
Reporter: rlpowell | Owner:
Type: bug | Status: closed
Priority: normal
#7290: Minor documentation fix for directory
--+-
Reporter: SimonHengel | Owner:
Type: bug | Status: closed
Priority: normal
#7486: dblatex can't build docs; fix included.
+---
Reporter: rlpowell | Owner:
Type: bug | Status: new
Priority: normal
#7486: dblatex can't build docs; fix included.
-+--
Reporter: rlpowell | Owner:
Type: bug | Status: merge
Priority: normal
#7290: Minor documentation fix for directory
+---
Reporter: SimonHengel | Owner:
Type: bug | Status: merge
Priority: normal
#7290: Minor documentation fix for directory
---+
Reporter: SimonHengel| Owner:
Type: bug| Status: patch
Priority: normal
#5140: Fix LLVM backend for PowerPC
+---
Reporter: erikd| Owner: erikd
Type: task | Status: new
Priority: low | Milestone: 7.6.2
#7486: dblatex can't build docs; fix included.
+---
Reporter: rlpowell | Owner:
Type: bug | Status: new
Priority: normal
#7486: dblatex can't build docs; fix included.
+---
Reporter: rlpowell | Owner:
Type: bug | Status: new
Priority: normal
#7442: [PATCH] Fix broken -fPIC on Darwin/PPC
-+--
Reporter: PHO | Owner:
Type: bug | Status: patch
Priority: normal| Milestone
#7442: [PATCH] Fix broken -fPIC on Darwin/PPC
--+-
Reporter: PHO | Owner:
Type: bug | Status: closed
Priority: normal | Milestone
#7442: [PATCH] Fix broken -fPIC on Darwin/PPC
-+--
Reporter: PHO | Owner:
Type: bug | Status: patch
Priority: normal| Milestone
#7442: [PATCH] Fix broken -fPIC on Darwin/PPC
-+--
Reporter: PHO | Owner:
Type: bug | Status: infoneeded
Priority: normal| Milestone
#7442: [PATCH] Fix broken -fPIC on Darwin/PPC
+---
Reporter: PHO | Owner:
Type: bug | Status: new
Priority: normal | Component
#7442: [PATCH] Fix broken -fPIC on Darwin/PPC
+---
Reporter: PHO | Owner:
Type: bug | Status: patch
Priority: normal | Component
#7136: fix for os x package builder script
--+-
Reporter: carter | Owner:
Type: bug | Status: new
Priority: normal
#7136: fix for os x package builder script
--+-
Reporter: carter | Owner:
Type: bug | Status: closed
Priority: normal
#7136: fix for os x package builder script
--+-
Reporter: carter | Owner:
Type: bug | Status: new
Priority: normal
#5996: fix for CSE
-+--
Reporter: michalt | Owner: simonpj
Type: bug | Status: patch
Priority: normal| Milestone: 7.8.1
#7222: The text Possible fix: add an instance declaration for ... is redundant
and not usually helpful
---+
Reporter: maltem| Owner:
Type: bug | Status
#7290: Minor documentation fix for directory
--+-
Reporter: SimonHengel | Owner:
Type: bug | Status: new
Priority: normal
#5996: fix for CSE
-+--
Reporter: michalt | Owner: simonpj
Type: bug | Status: patch
Priority: normal| Milestone: 7.8.1
#7222: The text Possible fix: add an instance declaration for ... is redundant
and not usually helpful
-+--
Reporter: maltem| Owner:
Type: bug | Status: new
#7222: The text Possible fix: add an instance declaration for ... is redundant
and not usually helpful
--+-
Reporter: maltem| Owner:
Type: bug | Status: new
#7222: The text Possible fix: add an instance declaration for ... is redundant
and not usually helpful
--+-
Reporter: maltem| Owner:
Type: bug | Status: new
#7136: fix for os x package builder script
---+
Reporter: carter | Owner:
Type: bug | Status: new
Priority: normal | Milestone
#7136: fix for os x package builder script
--+-
Reporter: carter | Owner:
Type: bug | Status: closed
Priority: normal
#7136: fix for os x package builder script
-+--
Reporter: carter | Owner:
Type: bug | Status: new
Priority: normal
#7136: fix for os x package builder script
-+--
Reporter: carter | Owner:
Type: bug | Status: new
Priority: normal
#5669: Fix test 5558 for Mac OS X 10.5
--+-
Reporter: thorkilnaur | Owner: pcapriotti
Type: bug | Status: closed
Priority: normal | Milestone: 7.6.1
Component
#5996: fix for CSE
-+--
Reporter: michalt | Owner: simonpj
Type: bug | Status: patch
Priority: normal| Milestone
#3940: Propagate bug fix into new code generator
-+--
Reporter: simonpj | Owner:
Type: bug | Status: new
Priority: low
#3940: Propagate bug fix into new code generator
---+
Reporter: simonpj | Owner:
Type: bug | Status: closed
Priority: low
This release fixes a problem where the GHCi integration
would break when the first command set was from the
debug scratch pane.
Source is in Hackage and https://github.com/leksah
Binary Installers
Use ghc --version to work out which one you need.
OS X
#6126: Fix risk of dead-lock in documentation of Control.Concurrent
+---
Reporter: basvandijk | Owner:
Type: bug| Status: closed
Priority
#6126: Fix risk of dead-lock in documentation of Control.Concurrent
-+--
Reporter: basvandijk| Owner:
Type: bug | Status: new
Priority
#6126: Fix risk of dead-lock in documentation of Control.Concurrent
-+--
Reporter: basvandijk| Owner:
Type: bug | Status: new
Priority
#6126: Fix risk of dead-lock in documentation of Control.Concurrent
---+
Reporter: basvandijk | Owner:
Type: bug| Status: new
Priority: normal
#5996: fix for CSE
-+--
Reporter: michalt | Owner:
Type: bug | Status: patch
Priority: normal | Component
#5996: fix for CSE
-+--
Reporter: michalt | Owner:
Type: bug | Status: patch
Priority: normal | Component
#5996: fix CSE
-+--
Reporter: michalt | Owner:
Type: bug | Status: new
Priority: normal | Component
#5996: fix for CSE
-+--
Reporter: michalt | Owner:
Type: bug | Status: patch
Priority: normal | Component
untouched.
It's most convenient if bound to an editor key.
Recent major changes:
version 1.0.0
Change name from FixImports to fix-imports, which is more unixy.
Change ghc-pkg parsing from String to Text. It's noticeably faster.
Add a more flexible system for prioritizing imports. When
I used https://github.com/kennethreitz/osx-gcc-installer/downloads to
get a real gcc on Lion. Biggish download, but it worked. I've also
seen reports of success by self-compiling gcc, or by installing XCode
4 on top of an existing XCode 3 installation.
John L.
From: Eugene Kirpichov
On 11 Jan 2012, at 13:38, John Lato wrote:
I used https://github.com/kennethreitz/osx-gcc-installer/downloads to
get a real gcc on Lion. Biggish download, but it worked. I've also
seen reports of success by self-compiling gcc, or by installing XCode
4 on top of an existing XCode 3
Thanks, looks like I already succeeded by downloading xcode 3.
Now my original question remains - is such a change a good idea?
(I've already found the place in code where the fix has to be made; should
take an hour of work at most)
On Wed, Jan 11, 2012 at 6:07 PM, Hans Aberg haber...@telia.com
Hi Eugene,
I think I did run into this problem before, and had to turn of split-objs
temporarily to work around it. I'd appreciate a fix.
Best,
Ozgur
On 11 January 2012 14:14, Eugene Kirpichov ekirpic...@gmail.com wrote:
Now my original question remains - is such a change a good idea?
(I've
On Wed, Jan 11, 2012 at 02:12, Eugene Kirpichov ekirpic...@gmail.comwrote:
I think a nice fix would be to employ gcc's ability to read options from a
file - gcc @file - and write overly long option strings into temp files.
What immediately occurs to me is, what if the problem (or another
...@gmail.comwrote:
I think a nice fix would be to employ gcc's ability to read options from
a file - gcc @file - and write overly long option strings into temp files.
What immediately occurs to me is, what if the problem (or another
manifestation of same) occurs in the ld step? OS X's ld(1) doesn't have
On Wed, Jan 11, 2012 at 14:50, Eugene Kirpichov ekirpic...@gmail.comwrote:
Do you think that what I originally proposed is still a good thing to have
before implementing your solution? (it definitely would be for myself, as
it's easier to do and I'd then quicker become able to build my
it compiles fine
too, and it compiles fine *with* -fsplit-objs on other OS - so perhaps the
reason is in mac's tempfile name generation (they're longer than on other
platforms) or something.
Anyway.
I think a nice fix would be to employ gcc's ability to read options from a
file - gcc @file - and write
on other OS - so perhaps the
reason is in mac's tempfile name generation (they're longer than on other
platforms) or something.
Anyway.
I think a nice fix would be to employ gcc's ability to read options from a
file - gcc @file - and write overly long option strings into temp files.
It'd
#5669: Fix test 5558 for Mac OS X 10.5
+---
Reporter: thorkilnaur | Owner:
Type: bug | Status: patch
Priority: normal | Milestone: 7.4.1
Component: Test Suite
#5669: Fix test 5558 for Mac OS X 10.5
+---
Reporter: thorkilnaur | Owner:
Type: bug | Status: new
Priority: normal | Component: Test Suite
Version
#5608: Fix T3807 for Mac OS X 10.5
--+-
Reporter: thorkilnaur | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 7.4.1
Component: Test Suite
#5608: Fix T3807 for Mac OS X 10.5
--+-
Reporter: thorkilnaur | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 7.4.1
Component: Test Suite
#5608: Fix T3807 for Mac OS X 10.5
--+-
Reporter: thorkilnaur | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Test Suite
#5606: Fix validate by moving {-# OPTIONS -fno-warn-tabs #-}
-+--
Reporter: thorkilnaur | Owner:
Type: bug | Status: new
Priority: normal
#5606: Fix validate by moving {-# OPTIONS -fno-warn-tabs #-}
-+--
Reporter: thorkilnaur | Owner:
Type: bug | Status: patch
Priority: normal
#5606: Fix validate by moving {-# OPTIONS -fno-warn-tabs #-}
-+--
Reporter: thorkilnaur |Owner: duncan
Type: bug | Status: patch
Priority
#5608: Fix T3807 for Mac OS X 10.5
+---
Reporter: thorkilnaur | Owner:
Type: bug | Status: new
Priority: normal | Component: Test Suite
Version: 7.3
#5608: Fix T3807 for Mac OS X 10.5
+---
Reporter: thorkilnaur | Owner:
Type: bug | Status: patch
Priority: normal | Component: Test Suite
Version: 7.3
#5608: Fix T3807 for Mac OS X 10.5
--+-
Reporter: thorkilnaur | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Test Suite
#5606: Fix validate by moving {-# OPTIONS -fno-warn-tabs #-}
--+-
Reporter: thorkilnaur | Owner: duncan
Type: bug | Status: closed
Priority: normal
#5576: Fix to #5549 breaks integerConstantFolding
--+-
Reporter: daniel.is.fischer |Owner: simonpj
Type: bug| Status: new
Priority: highest
#5576: Fix to #5549 breaks integerConstantFolding
--+-
Reporter: daniel.is.fischer |Owner: simonpj
Type: bug| Status: new
Priority: highest
#5576: Fix to #5549 breaks integerConstantFolding
--+-
Reporter: daniel.is.fischer | Owner:
Type: bug| Status: new
Priority: normal
Hello!
Please be advised that clientsession 0.7.3.1 is vulnerable to timing
attacks [1]. We have just released a fix and it's already on Hackage
[2]. We advise all users of clientsession (and, consequently, Yesod)
to upgrade as soon as possible to a version = 0.7.3.1.
With a timing attack
On Mon, Oct 3, 2011 at 10:01 AM, Felipe Almeida Lessa
felipe.le...@gmail.com wrote:
With a timing attack a malicious user may be able to construct a valid
MAC for his message. However, the attacker is not able to recover the
MAC key or the encryption key. So you don't need to change your
On 09/08/2011 22:24, Eugene Kirpichov wrote:
Hi Simon,
I found a bug in alex-3.0 and I'm attaching a fixed source file -
templates/wrappers.hs (modified against alex-3.0 from cabal unpack).
Explanation:
I was installing bytestring-lexing 0.2.1 and it failed to install with
alex 3.0, which was
Hi Simon,
I found a bug in alex-3.0 and I'm attaching a fixed source file -
templates/wrappers.hs (modified against alex-3.0 from cabal unpack).
Explanation:
I was installing bytestring-lexing 0.2.1 and it failed to install with
alex 3.0, which was released on Aug 4.
It succeeded, however, with
#5140: Fix LLVM backend for PowerPC
-+--
Reporter: erikd |Owner: erikd
Type: task | Status: new
Priority: normal|Milestone: 7.4.1
Component
#5140: Fix LLVM backend for PowerPC
-+--
Reporter: erikd |Owner: erikd
Type: task | Status: new
Priority: normal|Milestone: 7.4.1
Component
On 12.07.2011 09:59, Evan Laforge wrote:
I meant more in the Before: ... After: ... sense ;-) (i.e. visually
being able to tell what your program does, rather than just a
description).
Oh, ok, I guess I can do that too:
Before:
module M where
import ZZ.Out.Of.Order
import qualified
1 - 100 of 438 matches
Mail list logo
