I think that we should try a different approach, forget about
the importing
mechanism, and make a single statement defining the intended semantics.
Section 1.2 (The Haskell Kernel) is the place. I propose adding the
following.
The translations given, and the identities given for t
(I sent a similar message a few days ago which got lost somewhere)
We have tried to express the semantics of some Haskell constructs by giving
a translation into "Kernel" Haskell (Report section 1.2).
This leads to difficulties because free variables in the translations can
be captured by the
|What if (the appropriate parts of) the standard prelude is
| explicitly *not* imported:
|
| import Prelude ()
| or
| import Prelude hiding(map)
|
| (see section 5.4.3).
|
|Are then the hidden parts of the standard prelude still available via
| n+k patterns, list comprehen
Some more questions concerning some constructs in Haskell:
What if (the appropriate parts of) the standard prelude is
explicitly *not* imported:
import Prelude ()
or
import Prelude hiding(map)
(see section 5.4.3).
Are then the hidden parts of the standard prelude still a
