RE: Windows build

Hi Simon, For the tests what Ben’s email forgot to say was that the build system doesn’t pick up on changes to Timeout. So you’d need to nuke it to get the fixes for timing related things: rm -rf testsuite/timeout/dist && rm -rf testsuite/timeout/install-inplace And rerun the tests should fix

Re: Separating typechecking and type error reporting in two passes?

Hi, Am Mittwoch, den 30.11.2016, 10:51 + schrieb Simon Peyton Jones via ghc-devs: > I very much doubt that you'll be able to discard the context > information from the type checker. Maybe some of it.   I can't say > exactly why, it's a gut feel for now. the gut feeling is warranted: There

Windows build

Thanks for all the work you've been doing on the Windows build. As requested by Tamar I removed ghc-tarballs, and reconfigured. Then I built from scratch. I get the following testsuite failures Simon Unexpected failures: ghci/prog003/prog003.runprog003 [bad exit code] (ghci)

Re: Testsuite and Python 3

The Python community is heavily pushing to get Python 2 out of normal use, so the only reason I can imagine of trying to maintain Python 2 compatibility is if people have written scripts atop GHC's test suites. I sort of doubt that's common. ᐧ On Wed, Nov 30, 2016 at 2:46 PM, Ben Gamari

Re: Separating typechecking and type error reporting in two passes?

Hi, Am Mittwoch, den 30.11.2016, 12:59 +0100 schrieb MarLinn via ghc-devs: > > But you are right that when the programmer sits there and waits for a > > result, that’s when snappyness is important. > > I had a random idea based on this observation: please allow me to re-iterate that my proposal

Re: Separating typechecking and type error reporting in two passes?

But you are right that when the programmer sits there and waits for a result, that’s when snappyness is important. I had a random idea based on this observation: (With a certain flag set) the compiler could follow the existing strategy until it has hit the first n errors, possibly with n=1.

RE: Separating typechecking and type error reporting in two passes?

| Then a second pass is done over the syntax tree. This pass does | keep | track of the context. Whenever it finds some error evidence, it | reports it. The syntax tree is a big type. A second pass would be a fairly big deal. But doable. You'd need to be able to look at the

Windows toolchain update

Hi Windows devs, The Windows GCC has been updated to 6.2.0 and binutils to 2.27. At some point please rebuild using these binaries. Do throw away your old toolchain cache before getting the new one: rm -rf ghc-tarballs && ./configure --enable-tarballs-autodownload The plan is to ship these

Re: Separating typechecking and type error reporting in two passes?

> Il giorno 29 nov 2016, alle ore 17:52, Joachim Breitner > ha scritto: > > Hi, > > I guess the claim is still true: Think about just the amount of code > you compile when you install your dependencies. > > But you are right that when the programmer sits there and