Re: Heads up: top level `make test` now runs the full testsuite

> Does this mean that full testsuite run has no broken tests? I vaguely recall > that some time ago a > couple of tests were broken. No, some tests are still broken. ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/

Re: Heads up: top level `make test` now runs the full testsuite

> Typing `make test` in the ghc root directory now runs the full > testsuite Does this mean that full testsuite run has no broken tests? I vaguely recall that some time ago a couple of tests were broken. Janek --- Politechnika Łódzka Lodz University of Technology Treść tej wiadomości zawiera i

Re: Hoopl and Arrows

Thomas, I did some stuff with Hoopl a few years ago as part of my Master's thesis ("Using Dataflow Optimization Techniques with a Monadic Intermediate Language"). In Chapter 3 ("The Hoopl Library"), I wrote up an overview of Hoopl and work through a new example (new at the time, at least). You ca

Re: Fwd: EvTerms and how they are used

Hello, I've seen instances of this problem show up over and over again, and I think that there is a more principled solution, based on the idea of `improvement`. The idea is to allow programmers to specify custom improvements. Functional dependencies are one way to do this, but there is no reason

RE: Hoopl and Arrows

Thomas Hoopl works on control flow graphs, whereas Core is lambda calculus. I really don’t think Hoopl is going to be any good for optimising Core. Ask the ghc-devs mailing list too. Someone there has been writing about arrows recently (take a look at the archive). Simon From: Thomas Berekn

Heads up: top level `make test` now runs the full testsuite

Typing `make test` in the ghc root directory now runs the full testsuite, just like it already did in the `testsuite/tests` directory. If you want to run the fast testsuite, use the new targets `make fasttest` or `make fast`. The `validate` script still runs the same tests as before (depending on

Re: Fwd: EvTerms and how they are used

Hi Adam, again thank you for your extensive and patient answer! It's a bit hard to know exactly what is going on without the full code, > but I think what is happening is this: you have an unsolved constraint > `Polymonad Identity n_abpq Identity` and your plugin provides an > evidence term of ty

Pattern matching and GADTs

GHC developers You may be interested in this paper, submitted to ICFP GADTs meet their match: pattern-matching warnings that account for GADTs, guards, and laziness, with Georgios Karachalias, Tom Schrijvers, and Dimitrios Vytinio

RE: Allowing rules to depend upon SimplCont

Simon Peyton Jones writes: > | > Is there a wiki page that describes this project? > | > - goals, and motivation > | > - design of the change > | > - any implementation notes > | > > | Not that I'm aware of. I can perhaps fix this. > > Yes please! It is SO helpful. > How does this [1] l

RE: Allowing rules to depend upon SimplCont

| > Is there a wiki page that describes this project? | > - goals, and motivation | > - design of the change | > - any implementation notes | > | Not that I'm aware of. I can perhaps fix this. Yes please! It is SO helpful. Simon ___ ghc-devs

RE: Allowing rules to depend upon SimplCont

Simon Peyton Jones writes: > Ben > > Is there a wiki page that describes this project? > - goals, and motivation > - design of the change > - any implementation notes > Not that I'm aware of. I can perhaps fix this. > I've lost context and #9661 is too long to suck up. A wiki page can > car

RE: Allowing rules to depend upon SimplCont

Ben Is there a wiki page that describes this project? - goals, and motivation - design of the change - any implementation notes I've lost context and #9661 is too long to suck up. A wiki page can carefully explain the story, without all the to-and-fro. | 1. Pass a dummy `SimplCont` (probab