Following Bryan's suggestion I've improved GHC's error message when there's a
module cycle:
Module imports form a cycle:
module `Foo4' imports `Foo'
which imports `Foo2'
which imports `Foo3'
which imports `Foo4'
Simon
|
For use at high school level, I would imagine that you would want to build a special distribution anyway. One that for example already includes packages, such as Gloss, that would be useful in teaching children programming in Haskell without they having to go through learning to use cabal (which
malcolm.wallace:
For use at high school level, I would imagine that you would want to build a
special distribution anyway. One that for example already includes packages,
such as Gloss, that would be useful in teaching children programming in
Haskell without they having to go through
I ran into some more code like this, and I realized there was something
pretty important: the majority of let-bindings do not have any free varaibles.
They could very well be floated to the top level without having to make any
source level changes.
So maybe let should be generalized, if no free
That is an interesting thought. As it happens, each binding records what its
free variables are, so it would not be hard to check whether all the free
variables were top-level-bound.
Of course, it would make the rule a bit more complicated. Rather than
only top level bindings are
On 14/06/2011 14:28, Simon Peyton-Jones wrote:
That is an interesting thought. As it happens, each binding records what its
free variables are, so it would not be hard to check whether all the free
variables were top-level-bound.
Of course, it would make the rule a bit more complicated.
Following up on the notion that Hugs might suit the casual introductory
user better - I see that while you can find it online as a pre-built
package, you're normally advised (haskell.org, Kent CS dept, etc.) to
build it via MacPorts - which requires Xcode.
I mention this because if anyone is
On Wed, Jun 8, 2011 at 11:26 PM, David Terei davidte...@gmail.com wrote:
I would suggest it be put under the Commentary/Compiler.
Here's a first draft:
http://hackage.haskell.org/trac/ghc/wiki/MemcpyOptimizations
Feel free to point out things that need clarification.
Cheers,
Johan
