Re: Reading floating point

2016-10-10 Thread David Feuer
It may currently be true for floats, but it's never been true in general, particularly with regard to records. Read is not actually designed to parse Haskell; it's for parsing "Haskell-like" things. Because it, unlike a true Haskell parser, is type-directed, there are somewhat different

Re: when building latest GHC on Mac with Xcode 8: Symbol not found: _clock_gettime

2016-10-10 Thread John Leo
Thanks very much Brandon for your fast reply! That did the trick. I had to rerun configure as well since when I didn't do that I got a different but seemingly related error. But after clean, configure and make everything seems to work again. John On Mon, Oct 10, 2016 at 8:27 PM, Brandon

Re: Reading floating point

2016-10-10 Thread David Feuer
I fully expect this to be somewhat tricky, yes. But some aspects of the current implementation strike me as pretty clearly non-optimal. What I meant about going through Rational is that given "625e-5", say, it calculates 625%10, producing a fraction in lowest terms, before calling

GHC 8.0.2 status

2016-10-10 Thread Ben Gamari
Hello GHCers, Thanks to the work of darchon the last blocker for the 8.0.2 release (#12479) has nearly been resolved. After the fix has been merged I'll be doing some further testing of the ghc-8.0 branch and cut a source tarball for 8.0.2-rc1 later this week. If you intend on offering a binary

RE: [Diffusion] [Build Failed] rGHCa6111b8cc14a: More tests for Trac #12522

2016-10-10 Thread Simon Peyton Jones via ghc-devs
This says “stat not good enough” for “max_bytes_used” on T1969. I pushed a “T1969 is ok” patch recently, because it IS ok on my (64-bit Linux) machine. If it’s not ok for our CI infrastructure, by all means un-push it or something. Simon From: nore...@phabricator.haskell.org

Re: Default options for -threaded

2016-10-10 Thread Eric Seidel
Ah, I'm sorry, I believe I was thinking of -qm, which is supposed to prevent threads from being moved. I forgot these were separate options! And the latest version of the User's Guide includes a comment about -qm > This option is probably only of use for concurrent programs that explicitly >

Re: Default options for -threaded

2016-10-10 Thread Phyx
Oh, this is surprising, I must admit I haven't tried forkIO, but with forkOS is doesn't move the threads across capabilities. Do you know if this is by design or a bug? On Sat, Oct 8, 2016 at 6:13 PM, Eric Seidel wrote: > I would prefer keeping -N1 as a default, especially now

Re: Default options for -threaded

2016-10-10 Thread Phyx
Oops, sorry, only just now seen this. It seems my overly aggressive filters couldn't decide where to put the email :) I do agree to some extend with this. I'd prefer if I made a mistake for my system not to hang. The one downside to this default though is that you can't just hand a program over

Re: Reading floating point

2016-10-10 Thread Yitzchak Gale
The way I understood it, it's because the type of "floating point" literals is Fractional a => a so the literal parser has no choice but to go via Rational. Once you have that, you use the same parser for those Read instances to ensure that the result is identical to what you would get if you

Re: Allow top-level shadowing for imported names?

2016-10-10 Thread Yitzchak Gale
Michael Sloan wrote: > It is really good to think in terms of a cleverness budget... > Here are the things I see in favor of this proposal: > > 1) It is common practice to use -Wall... > 2) It lets us do things that are otherwise quite inconvenient... You missed the most important plus: 0) It