#2907: generalized newtype deriving not working with polymorphic component
-+--
Reporter: jeltsch |Owner:
Type: feature request | Status: closed
#2759: Data.Generics.ConstrRep isn't general enough
--+-
Reporter: guest |Owner: dreixel
Type: bug| Status: assigned
Priority: normal
#2416: Optimization defeated by merging module into main
---+
Reporter: sedillard |Owner:
Type: bug | Status: new
Priority: normal |
#2911: Error messages have the wrong qualified names
-+--
Reporter: igloo |Owner:
Type: bug | Status: new
Priority: normal|
#2659: Add sortOn and other *On functions
-+--
Reporter: twanvl|Owner:
Type: proposal | Status: new
Priority: normal|
#2905: require -XGADTs in order to pattern-match GADTs
-+--
Reporter: guest| Owner:
Type: proposal | Status: new
Priority: normal
#2911: Error messages have the wrong qualified names
-+--
Reporter: igloo |Owner:
Type: bug | Status: new
Priority: normal|
#2912: GHCi bug: bus error when executing some gsl-random code
---+
Reporter: fdeweerdt | Owner:
Type: bug| Status: new
Priority: normal | Milestone:
#2912: GHCi bug: bus error when executing some gsl-random core
--+-
Reporter: fdeweerdt | Owner:
Type: bug| Status: new
Priority: normal | Component: GHCi
#789: BCOs can only have 64k instructions: linkBCO: = 64k insns in BCO
+---
Reporter: simonpj |Owner:
Type: bug | Status: new
Priority: normal |Milestone:
#2909: long list of names -linkBCO: = 64k insns in BCO
-+--
Reporter: jowens|Owner:
Type: bug | Status: closed
Priority: normal
#2422: Unrelated instance foils optimizer
--+-
Reporter: sedillard |Owner:
Type: bug| Status: new
Priority: normal |Milestone: 6.10 branch
Component:
#2746: Documentation for Haskell 98 modules is empty
-+--
Reporter: simonmar |Owner:
Type: bug | Status: new
Priority: high |
#2746: Documentation for Haskell 98 modules is empty
-+--
Reporter: simonmar |Owner:
Type: bug | Status: new
Priority: high |
| Thanks very much for this. I would never have guessed to use
| -XRelaxedPolyRec given the error message.
|
| Is it worth noting it here
| http://haskell.org/haskellwiki/Upgrading_packages#Changes_to_GADT_matching
| or is it something that has always existed with GADTs and I just didn't
| trip
On Mon, Dec 29, 2008 at 05:07:22PM +0100, Bertram Felgenhauer wrote:
Simon Peyton-Jones wrote:
This is odd (to me). The permanently bound stuff applies only to
*synchronous* exceptions, which thread-killing is not. Simon M will
have more to say when he gets back
This is true when
Hi John,
On Mon, Dec 15, 2008 at 08:17:56AM -0800, John MacFarlane wrote:
I noticed a difference in how hang works between pretty-1.0.0.0 and
pretty-1.0.1.0. I think it's a bug. If this isn't the right place to
report it, please let me know where I should.
The best place at the moment is in
Ahn == Ahn, Ki Yung kya...@gmail.com writes:
Ahn P.S. If you happen to be a local Korean expert on this matter,
Ahn sorry for my ignorance, and I'd be happy to forward their inquiry
Ahn to you!
Probably not Korea-based, but 1st class Haskell hackers:
http://www.well-typed.com/
Sincerely,
Classic FRP (CFRP, like Fran, FAL, Reactive, Grapefruit?...)
exposes signals as first class values.
Arrow based FRP (AFRP, like Fruit, Yampa...) hides signals as first
class values; instead the signal transformers are the first class
values.
Can I conclude that it would theoretically be possible
Hello,
I have the following:
B.intercalate $ B.intercalate
ByteString
[ByteString]
[ByteString]
I get a type error with this. If I comment out the 2nd B.intercalate
and the third parameter I get no type errors.
2009/1/5 Galchin, Vasili vigalc...@gmail.com:
Hello,
I have the following:
B.intercalate $ B.intercalate
ByteString
[ByteString]
[ByteString]
I get a type error with this. If I comment out the 2nd
Hi Max,
That is what should happen The inner B.intercalate will produce
the ByteString to be used by the B.intercalate. ??
Vasili
On Mon, Jan 5, 2009 at 12:13 PM, Max Rabkin max.rab...@gmail.com wrote:
2009/1/5 Galchin, Vasili vigalc...@gmail.com:
Hello,
I have the
Did you mean:
B.intercalate (B.intercalate ByteString [ByteString]) [ByteString]
($) applies all the way to the right, so you were giving the inner
intercalate two lists of ByteString.
-Ross
On Jan 5, 2009, at 1:17 PM, Galchin, Vasili wrote:
Hi Max,
That is what should happen
Ketil Malde ke...@malde.org wrote:
Implicit importing: submodule syntax implies adding an import
The.Module.Name line at that point in the containing file.
I'm not sure I agree with that, I don't see why we shouldn't treat
these modules as ordinary modules. One of the motivations
On Mon, Jan 5, 2009 at 10:17 AM, Galchin, Vasili vigalc...@gmail.com wrote:
Hi Max,
That is what should happen The inner B.intercalate will produce
the ByteString to be used by the B.intercalate. ??
Vasili
Of course. My mistake. Ross Mellgren seems to be on the money though.
yep ... that is exactly what I meant!! so can I use more $'s or must I use
parens (as you did) to disambiguate?
Vasili
On Mon, Jan 5, 2009 at 12:18 PM, Ross Mellgren rmm-hask...@z.odi.ac wrote:
Did you mean:
B.intercalate (B.intercalate ByteString [ByteString]) [ByteString]
($) applies all
In this case you have to use parens -- two dollar signs, like this
B.intercalate $ B.intercalate ByteString [ByteString] $ [ByteString]
would also not type check -- it is exactly equivalent to your first
example:
B.intercalate (B.intercalate ByteString [ByteString] ([ByteString]))
just
2009/1/5 Ross Mellgren rmm-hask...@z.odi.ac:
If for some reason you absolutely need to avoid parentheses (mostly as a
thought exercise, I guess), you'd have to have a flipped version of
intercalate:
Or a version of ($) that associates differently.
infixl 0 $$
f $$ x = f x
*Main
Thank you everybody!
Vasili
On Mon, Jan 5, 2009 at 12:57 PM, David Menendez d...@zednenem.com wrote:
2009/1/5 Ross Mellgren rmm-hask...@z.odi.ac:
If for some reason you absolutely need to avoid parentheses (mostly as a
thought exercise, I guess), you'd have to have a flipped version of
Ketil Malde ke...@malde.org wrote:
Achim Schneider bars...@web.de writes:
import [qualified] module Foo [as F] [hiding(baz)] where
bar = undefined
baz = bar
Why do you want the 'where' there? Why not simply treat a file
Foo.Bar as a concatenation of module Foo.Bar and
On Thu, Jan 1, 2009 at 8:32 PM, Bryan O'Sullivan b...@serpentine.com wrote:
On Wed, Dec 31, 2008 at 11:42 AM, Levi Greenspan
greenspan.l...@googlemail.com wrote:
Hence my question - is it likely that GHC will support epoll in 2009?
Yes. I'm working on a patch at the moment.
Awesome! Please
On Mon, Jan 5, 2009 at 10:09 AM, Peter Verswyvelen bugf...@gmail.comwrote:
Classic FRP (CFRP, like Fran, FAL, Reactive, Grapefruit?...)
exposes signals as first class values.
Arrow based FRP (AFRP, like Fruit, Yampa...) hides signals as first
class values; instead the signal transformers are
Generalizing the previous post, with:
-
{-# LANGUAGE GADTs #-}
module Equ where
data a:==:b where
Equ :: (a ~ b) = a:==:b
symm :: (a:==:a)
symm = Equ
refl :: (a:==:b) - (b:==:a)
refl Equ = Equ
trans :: (a:==:b) -
Achim Schneider bars...@web.de wrote:
Ketil Malde ke...@malde.org wrote:
Achim Schneider bars...@web.de writes:
import [qualified] module Foo [as F] [hiding(baz)] where
bar = undefined
baz = bar
Why do you want the 'where' there? Why not simply treat a file
Foo.Bar as a
On Mon, Jan 5, 2009 at 3:16 PM, Brandon S. Allbery KF8NH
allb...@ece.cmu.edu wrote:
On 2009 Jan 5, at 13:57, David Menendez wrote:
2009/1/5 Ross Mellgren rmm-hask...@z.odi.ac:
If for some reason you absolutely need to avoid parentheses (mostly as a
thought exercise, I guess), you'd have to
Robin Green gree...@greenrd.org wrote:
Whereas, each of these academics might be oblivious (or almost
oblivious) to the other two critiques.
And a load full of arguments why those other critiques are
irrelevant? ;)
--
(c) this sig last receiving data processing entity. Inspect headers
for
Achim Schneider bars...@web.de writes:
import [qualified] module Foo [as F] [hiding(baz)] where
bar = undefined
baz = bar
Why do you want the 'where' there?
Because the module definition syntax is module Foo[(exports] where...
technically, it's not necessary, but it's nice.
On 2009 Jan 5, at 13:57, David Menendez wrote:
2009/1/5 Ross Mellgren rmm-hask...@z.odi.ac:
If for some reason you absolutely need to avoid parentheses (mostly
as a
thought exercise, I guess), you'd have to have a flipped version of
intercalate:
Or a version of ($) that associates
Hi Adrian
On Wed, Dec 17, 2008 at 11:44:14AM +0100, Adrian Neumann wrote:
I have a strange problem with interact on OS X (ghc 6.10.1). It
seems to garble stdin.
See the After using getContents section of
http://www.haskell.org/ghc/docs/latest/html/users_guide/ghci-faq.html
Thanks
On Mon, Jan 5, 2009 at 1:48 PM, Peter Robinson thaldy...@gmail.com wrote:
Hello,
One thing that's been bothering me about MonadError monads is
the non-portability of code that uses a custom Error type. Meaning, if I
have libraries A and B that use different error types, I won't be able to
On Mon, Jan 5, 2009 at 2:13 PM, Luke Palmer lrpal...@gmail.com wrote:
On Mon, Jan 5, 2009 at 1:48 PM, Peter Robinson thaldy...@gmail.comwrote:
Hello,
One thing that's been bothering me about MonadError monads is
the non-portability of code that uses a custom Error type. Meaning, if I
have
I think I found a solution to this, if you're still looking for one. See
attached code. It uses a rose tree zipper where tree depth is manhattan
distance from origin and forest width is nodes around concentric
diamonds. The code is straightforward. Polar coords (RK) are stored in
node label,
On Mon, Jan 5, 2009 at 2:13 PM, Luke Palmer lrpal...@gmail.com wrote:
On Mon, Jan 5, 2009 at 1:48 PM, Peter Robinson thaldy...@gmail.com
wrote:
Hello,
One thing that's been bothering me about MonadError monads is
the non-portability of code that uses a custom Error type. Meaning, if I
On Mon, Jan 5, 2009 at 2:13 PM, Luke Palmer lrpal...@gmail.com wrote:
Then your example can become::
func = (mapError Left funcA mapError Right funcB) `catchError` (\e -
...)
Luke
Oh bother! My new year's resolution: think before I speak.
While I do think this is the right answer, it
On Mon, 5 Jan 2009, Luke Palmer wrote:
Oh bother! My new year's resolution: think before I speak.
While I do think this is the right answer, it is not the right answer in the
status quo. This is
because ErrorT e m is only a monad when e is an Error, which Either (and most
types) are not.
On Tue, Dec 16, 2008 at 04:24:25PM +0100, Christian Maeder wrote:
Donald Halomoan wrote:
I am waiting for GHC 6.10. 1 binary for Solaris i86. Thanks.
You could try mine:
When using any of -O, -O1, -O2 with the Debian binary build of GHC 6.6,
trace shows that the expression
if (lr ll) then False else True
is (at least partially) evaluated, but the value returned is always True,
even though trace reports that (lr ll) is True. When I use only the
On Mon, Jan 5, 2009 at 4:34 PM, Murray Gross mgros...@verizon.net wrote:
When using any of -O, -O1, -O2 with the Debian binary build of GHC 6.6,
trace shows that the expression
if (lr ll) then False else True
is (at least partially) evaluated, but the value returned is always
For the 2D grid zipper above, moving around is O(1) but update is O(log
n). This is acceptable; also because I'm quite confident that a zipper
for a 2D grid with everything O(1) does not exist. I can prove that for
a special case and should probably write it down at some point.
Really? My
-- bytestring-trie 0.1.2 (bugfix)
Another bugfix release for efficient finite maps from (byte)strings to
values. Release early, release often.
-- Changes
No unsafe perform (except what may be hidden in trace), nothing, fancy, no
gimmicks (very pedestrian, even heavy-handed) code. Complete code is
attached (I don't have smaller snippets, because I just discovered the
problem).
Best,
Murray Gross
On Mon, 5 Jan 2009, Luke Palmer wrote:
Dear haskeller,
Can I destructive rebind a local variable like this
import System.Directory
test filename = do
is_dir - doesDirectoryExist filename
let filename = if not is_dir then filename else filename
putStrLn $ filename ++ filename
main = test .
in GHCi 6.10.1 on WinXP,
2009/1/6 Wang, Chunye (NSN - CN/Beijing) chunye.w...@nsn.com
Dear haskeller,
Can I destructive rebind a local variable like this
import System.Directory
test filename = do
is_dir - doesDirectoryExist filename
let filename = if not is_dir then filename else filename
Nope. The
Hi Luke
Thank you ! I got it :)
Best Regards
Chunye Wang chunye.w...@nsn.com
From: ext Luke Palmer [mailto:lrpal...@gmail.com]
Sent: Tuesday, January 06, 2009 3:44 PM
To: Wang, Chunye (NSN - CN/Beijing)
Cc: Haskell-Cafe@haskell.org
Subject: Re:
54 matches
Mail list logo
