I'm posting this because Richard said it would be the best place to raise
this issue. I know it's a little bit late in the GHC8 development process,
but I would like to get the idea out there.
To my knowledge, in GHC8, turning on VisibleTypeApplication will also turn
on AllowAmbiguousTypes. I thin
> On 14 Mar 2016, at 8:06 pm, Simon Peyton Jones wrote:
>
> But my rough answer would be: IORefs are really only meant for
> single-threaded work. Use STM for concurrent communication.
You can also use atomicModifyIORef for simple things.
> Why can’t GHC tighten the semantics of IORefs so
Hi Madan,
Yes, GHC, like Java, is an "unsafe language" currently ;-). It does not
protect its abstractions against buggy programs. Namely both Haskell and
Java do not protect semi-colon/(>>).
Really, we should probably have some additional monad to distinguish
data-race-free (DRF) IO programs f
On Wed, Mar 9, 2016 at 7:33 PM, Ben Gamari wrote:
>
> Unfortunately -fobject-code is necessary when loading GHC in GHCi as the
> bytecode interpreter doesn't support unboxed tuples, which various GHC
> modules use.
>
There's a ticket for that: https://ghc.haskell.org/trac/ghc/ticket/1257
("Byteco
Simon Peyton Jones writes:
> Great. Is there a clearly-articulated design on a wiki page?
>
The design for the relevant GHC extension is here [1].
Cheers,
- Ben
[1] https://ghc.haskell.org/trac/ghc/wiki/InstanceTemplates
signature.asc
Description: PGP signature
___
Great. Is there a clearly-articulated design on a wiki page?
Simon
| -Original Message-
| From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of
| Sylvain Henry
| Sent: 11 March 2016 20:59
| To: Ben Gamari
| Cc: ghc-devs@haskell.org
| Subject: Re: Fwd: Reducing boilerp
Maclan
I’m glad you enjoyed the awkward squad paper.
I urge you to write to the Haskell Café mailing list and/or ghc-devs. Lots of
smart people there. Ryan Newton is working on this kind of stuff; I’ve cc’d
him.
But my rough answer would be: IORefs are really only meant for single-threaded
