On 26/08/13 10:00, Jan Stolarek wrote:
1. This adds a new constraint on the dataflow algorithm, namely that it
must traverse the blocks in the correct order.
I don't follow. From what I've seen in the code Hoopl orders blocks using
depth-first traversal.
For backwards analysis it reverses that
> 1. This adds a new constraint on the dataflow algorithm, namely that it
> must traverse the blocks in the correct order.
I don't follow. From what I've seen in the code Hoopl orders blocks using
depth-first traversal.
For backwards analysis it reverses that order. I don't think that proposed
c
ated (more clearly I hope)
S
| -Original Message-
| From: Simon Marlow [mailto:marlo...@gmail.com]
| Sent: 22 August 2013 15:14
| To: Jan Stolarek
| Cc: ghc-devs; Simon Peyton-Jones; n...@cs.tufts.edu; d...@cs.tufts.edu;
| Edward Z. Yang
| Subject: Re: Changes in Hoopl
|
| Hi Jan,
|
| On 2
imon Peyton-Jones"
Do: "Simon Marlow" , "Jan Stolarek"
DW: "ghc-devs" , n...@cs.tufts.edu, d...@cs.tufts.edu,
"Edward Z. Yang"
Wysłane: czwartek, 22 sierpień 2013 17:44:11
Temat: RE: Changes in Hoopl
I have elaborated (more clearly I hope)
S
| -Or
I have elaborated (more clearly I hope)
S
| -Original Message-
| From: Simon Marlow [mailto:marlo...@gmail.com]
| Sent: 22 August 2013 15:14
| To: Jan Stolarek
| Cc: ghc-devs; Simon Peyton-Jones; n...@cs.tufts.edu; d...@cs.tufts.edu;
| Edward Z. Yang
| Subject: Re: Changes in Hoopl
> But you don't say what you want to do with that observation.
> Could you list the API changes you want to make?
Sure, I'll write down the exact changes I'm thinking of, but probably next week
- I'll let you know that I updated the wiki page.
Janek
Hi Jan,
On 22/08/13 14:01, Jan Stolarek wrote:
Me and Simon PJ had some discussion about modifying Hoopl. I summarized that
discussion on a wiki page:
http://ghc.haskell.org/trac/ghc/wiki/Hoopl/Cleanup
I'd like to implement changes once there's a consensus on which changes exactly
do we want
Hey Janek,
as a remark, Hoopl is the only library in GHC that defines its own "<*>"
operation, which will clash with the AMP. Hoopl's <*> is conceptually
just `mappend`, so if you're doing a large-scale refactoring of the
module maybe consider adding a suitable Monoid instance to replace <*>
with
Me and Simon PJ had some discussion about modifying Hoopl. I summarized that
discussion on a wiki page:
http://ghc.haskell.org/trac/ghc/wiki/Hoopl/Cleanup
I'd like to implement changes once there's a consensus on which changes exactly
do we want in Hoopl.
Janek
___
