- Haskell-Cafe - Haskell.org

RE: Survival of generic-classes in ghc
by Simon Peyton-Jones 25 Feb '02

25 Feb '02

| As long as we're reifying everything in sight, why not | simplify the design problem and reify the constructor dictionaries? Because the generic function may be building the contructor not taking it apart. (Think of a generic read function). So there is no reified constructor to deconstruct. This is discussed in the generic classes paper. It has to be done by recursion over the type. It's emphatically not just an efficiency issue. Simon

1 0

(no subject)
by Tom Bevan 25 Feb '02

25 Feb '02

Hi, I've come across this sort of data constructor below many times but I'm not really sure how to use it. Can someone please point me to the right section in the documentation? In particular, I want to know how to create a calendar time and how to access the fields . Tom data CalendarTime = CalendarTime { ctYear :: Int, ctMonth :: Month, ctDay, ctHour, ctMin, ctSec :: Int, ctPicosec :: Integer, ctWDay :: Day, ctYDay :: Int, ctTZName :: String, ctTZ :: Int, ctIsDST :: Bool } deriving (Eq, Ord, Read, Show)

2 1

Re: (no subject)
by Ashley Yakeley 25 Feb '02

25 Feb '02

At 2002-02-24 22:46, Tom Bevan wrote: >I've come across this sort of data constructor below many times but I'm >not really sure how to use it. Can someone please point me to the right >section in the documentation? http://haskell.org/onlinereport/decls.html#sect4.2.1 "Labelled Fields" >In particular, I want to know how to create a calendar time and how to >access the fields . > >Tom > >data CalendarTime = CalendarTime { > ctYear :: Int, > ctMonth :: Month, > ctDay, ctHour, ctMin, ctSec :: Int, > ctPicosec :: Integer, > ctWDay :: Day, > ctYDay :: Int, > ctTZName :: String, > ctTZ :: Int, > ctIsDST :: Bool > } deriving (Eq, Ord, Read, Show) Basically it's equivalent to this: data CalendarTime = CalendarTime Int Month Int Int Int Int Integer Day Int String Int Bool deriving (Eq, Ord, Read, Show); ctYear (CalendarTime x _ _ _ _ _ _ _ _ _ _ _) = x; ctMonth (CalendarTime _ x _ _ _ _ _ _ _ _ _ _) = x; ctDay (CalendarTime _ _ x _ _ _ _ _ _ _ _ _) = x; etc. ...but you can also use the labelled fields to construct: CalendarTime { ctYear = 2002, ctMonth = 2, ... } -- Ashley Yakeley, Seattle WA

1 0

Magnets supplier located.
by LEWIS＠haskell.org 24 Feb '02

24 Feb '02

1 0

if -> is a type constructor
by Cagdas Ozgenc 24 Feb '02

24 Feb '02

Greetings folks. If (->) is a type constructor, what does its definition look like, what data constructors does it have? How does it differ from other type constructors, or maybe it doesn't? Could someone give an explanation... Thanks for taking time.

2 1

Re: Graphs
by Jan-Willem Maessen 23 Feb '02

23 Feb '02

David Feuer <dfeuer(a)cs.brown.edu> writes: > I seem to remember an article about functional graph algorithms using > extra-lazy arrays. Anyone know if these arrays have appeared in any > mainstream implementation? I assume you're referring to this paper by Thomas Johnsson: @Article{lazyArray, author = {Johnsson, Thomas}, title = {Efficient Graph Algorithms Using Lazy Monolithic Arrays}, journal = JFP, year = 1998, volume = 8, number = 4, pages = {323--333}, month = {July} } He uses similar techniques to do whole-program flow analysis of Haskell programs, a clever bit of coding described in the following paper: @inproceedings{grinHeap, AUTHOR = "Johnsson, Thomas", TITLE = "Analysing Heap Contents in a Graph Reduction Intermediate Language.", booktitle = Proc # "Glasgow Functional Programming Workshop", address = "Ullapool 1990", MONTH = "August", YEAR = 1991 } The LazyArray library is part of the standard hbc distribution. The Eager Haskell compiler depends on it (you can get very nice static hash tables this way, among other things). As a result, I've done a port of the library to GHC (and, I think, hugs). I should note that most of the hints required to pull off the implementation were found in the "State in Haskell" paper by Simon PJ and John Launchbury. The library is available (along with a few other useful snippets, like universal splittable supplies) here: http://www.csg.lcs.mit.edu/~earwig/haskell-lib/ -Jan-Willem Maessen

2 1

Re: Monadic Call/CC?
by Ashley Yakeley 23 Feb '02

23 Feb '02

At 2002-02-23 07:55, Marcin 'Qrczak' Kowalczyk wrote: >It's in GHC in module MonadCont, together with a monad transformer >providing continuations and some instances. Could this sort of thing _please_ be added to <http://www.haskell.org/ghc/docs/latest/set/book-hslibs.html> or somewhere? Is this documented somewhere? -- Ashley Yakeley, Seattle WA

1 0

Re: Monadic Call/CC?
by Marcin 'Qrczak' Kowalczyk 23 Feb '02

23 Feb '02

Thu, 21 Feb 2002 19:36:13 -0800, Ashley Yakeley <ashley(a)semantic.org> pisze: > data ContMonad p a = MkContMonad ((a -> p) -> p); [...] It's in GHC in module MonadCont, together with a monad transformer providing continuations and some instances. -- __("< Marcin Kowalczyk * qrczak(a)knm.org.pl http://qrczak.ids.net.pl/ \__/ ^^ QRCZAK

1 0

Re: Monadic Call/CC?
by Ashley Yakeley 22 Feb '02

22 Feb '02

At 2002-02-22 01:36, Richard Uhtenwoldt wrote: >So, congratulations, you've written call/cc in Haskell. I think. Yes. test2 :: CPS (IO ()) (); test2 = do { liftM (putStr "aa\n"); ref <- liftM (newIORef Nothing); liftM (putStr "bb\n"); flag <- peirceM (\c -> do { liftM (putStr "cc\n"); liftM (writeIORef ref (Just c)); liftM (putStr "dd\n"); c True; liftM (putStr "ee\n"); return False; }); liftM (putStr "ff\n"); if (flag) then do { liftM (putStr "gg\n"); Just c' <- liftM (readIORef ref); liftM (putStr "hh\n"); c' False; liftM (putStr "ii\n"); } else do { liftM (putStr "jj\n"); } }; ContMonad> doMonadCPS test2 aa bb cc dd ff gg hh ff jj ...which shows that the continuation passed in by peirceM works both inside and outside the call. Changing "c' False" to "c' True" gave this endless iteration: ContMonad> doMonadCPS test2 aa bb cc dd ff gg hh ff gg hh ff gg hh ... I assume by the magic of Haskell's tail recursion, this won't eat up space. -- Ashley Yakeley, Seattle WA

1 0

Haskell problem
by Mark Wotton 22 Feb '02

22 Feb '02

Hi, I'm trying out some combinatorial parsers, and I ran into a slightly inelegant construction. To parse a sequence of things, we have a function like pThen3 :: (a->b->c->d) -> Parser a -> Parser b -> Parser c -> Parser d pThen3 combine p1 p2 p3 toks = [(combine v1 v2 v3, toks3) | (v1, toks1) <- p1 toks, (v2, toks2) <- p2 toks1, (v3, toks3) <- p3 toks2] The problem with this is that this structure has to be duplicated for pThen2, pThen4, and so on. These other forms are very similar to pThen3, but there seems to be no way to capture this in Haskell's type system, as the combine function has a different signature for each pThenX. (This is actually the first time the Haskell type system has got in my way rather than helping.) Is there a way around this problem? mrak

5 5