Dear Sir or Madam:
I was going to define a function within ghci, and the messages of
panic showed:
---
Prelude let f 1 = 1
C:\ghc\ghc-6.0\bin\ghc.exe: panic! (the `impossible' happened, GHC
version 6.0):
getLinkDeps No iface for [pkg]GHCziErr
Check out:
http://www.haskell.org/pipermail/glasgow-haskell-bugs/2003-June/003330.h
tml
| -Original Message-
| From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
| Behalf Of [EMAIL PROTECTED]
| Sent: 29 June 2003 11:17
| To: [EMAIL PROTECTED]
| Subject: ghc-6.0 on win32 panic
|
There seems to be a mistake in the handling of case, no?
Thanks,
Paul
$ ghci
___ ___ _
/ _ \ /\ /\/ __(_)
/ /_\// /_/ / / | | GHC Interactive, version 6.0, for Haskell 98.
/ /_\\/ __ / /___| | http://www.haskell.org/ghc/
\/\/ /_/\/|_| Type :? for help.
:info treats _a as an infix operator in ghci.
Prelude let _a = 'a'
Prelude :i _a
-- _a is a variable, defined at interactive:1
(_a) :: Char
should have not enclosed _a in parens.
--
Hal Daume III | [EMAIL PROTECTED]
Arrest this man, he talks in maths.
Am 23. Jun 2003 um 12:05 CEST schrieb Simon Marlow:
Could you explain how this works? writeChan doesn't update the count -
it should, right? But if it does, won't there be race conditions when
read write happen at the same time?
I updated the file at http://www.foldr.org/~stolz/Chan2.hs
On Friday, June 27, 2003, at 07:08 PM, Volker Stolz wrote:
[Moving to [EMAIL PROTECTED]
In local.haskell, you wrote:
I've been using sockets and handles with ghc-5.04.3.
The strange thing is now that when I make a handle
out of a socket and ask whether the handle is readable
or writable, it
In local.glasgow-haskell-users, you wrote:
I've been using sockets and handles with ghc-5.04.3.
The strange thing is now that when I make a handle
out of a socket and ask whether the handle is readable
or writable, it returns True for the former and False
for the latter, although sockets are
If you have a class like this
class FloatTraits a where
mantissa :: Int
then the type of mantissa is
mantissa :: forall a. FloatTraits a = Int
There's nothing wrong with this in principle; the difficulty is that
when you say
mantissa + 4
you aren't saying
If we could only figure out a good syntax for
(optional) type application, it would deal rather nicely with many of
these cases. Trouble is, '..' gets confused with comparisons. And
when there are multiple foralls, it's not obvious what order to supply
the type parameters.
What about
At 2003-06-30 01:55, Ralf Hinze wrote:
What about
mantissa (| Double |) + 4 ?
This would work perfectly with my method if (| Double |) were syntactic
sugar for (mkType :: Type Double) or similar. I really think it's the
most straightforward way of doing it and I hazard the easiest to
Hi
There's nothing wrong with this in principle; the difficulty is that
when you say
mantissa + 4
you aren't saying which float type to get the mantissa of. Earlier
messages have outlined workarounds, but in some ways the real solution
is to provide a syntax for type application.
Kind of a random question for today :).
We all know that we can write map in terms of foldr:
map f = foldr ((:) . f) []
as I understand it, this is essentially because foldr encapsulates all
primitive recursive functions and since map is primitive recursive, we
can implement it in terms of a
12 matches
Mail list logo
