Would something like John Meacham's class alias proposal (
http://repetae.net/recent/out/classalias.html) help alleviate this problem?
On Tue, Sep 30, 2014 at 5:02 PM, Brandon Allbery
wrote:
> On Tue, Sep 30, 2014 at 5:00 PM, Malcolm Wallace
> wrote:
>
>> How about doing the honest thing, and w
On Tue, Sep 30, 2014 at 5:00 PM, Malcolm Wallace
wrote:
> How about doing the honest thing, and withdrawing both packages in
> ghc-7.10? Haskell'98 is now 15 years old, and the 2010 standard was never
> really popular anyway.
There are apparently educators using both, although they're not used
How about doing the honest thing, and withdrawing both packages in ghc-7.10?
Haskell'98 is now 15 years old, and the 2010 standard was never really popular
anyway.
Regards,
Malcolm
On 30 Sep 2014, at 21:21, Austin Seipp wrote:
Hello developers, users, friends,
I'd like you all to weigh
I hate #1. Let's avoid if unless it's really crucial to some of our users.
Simon
| -Original Message-
| From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Austin
| Seipp
| Sent: 30 September 2014 21:21
| To: ghc-d...@haskell.org; glasgow-haskell-users@haskell.org
| Subject
Hello developers, users, friends,
I'd like you all to weigh in on something - a GHC bug report, that has
happened as a result of making Applicative a superclass of Monad:
https://ghc.haskell.org/trac/ghc/ticket/9590
The very condensed version is this: because haskell2010/haskell98
packages try t
Yes, that is the semantics I use for recursive module imports in jhc. And
you are right in that it does not accept those examples due to being unable
to bootstrap the least fixed point.
How would the 'as M' proposal interact? Would it actually be new entries in
the name table or rewritten as a mac
If there is to be such a language feature, I strongly feel it should be via
something like
module Long.Name.M( f, g, h ) as K where ...
I do not want to try to piggy-back on the possible meaning of a self-import;
it’s just asking for trouble, as Iavor points out.
Using “as M” in
Hello,
What semantics are you using for recursive modules? As far as I see, if
you take a least fixed point semantics (e.g. as described in "A Formal
Specification for the Haskell 98 Module System",
http://yav.github.io/publications/modules98.pdf ) this program is incorrect
as the module does not
