Re: Debugging GHC with GHCi

2017-01-08 Thread Ben Gamari
Thomas Jakway writes: > I want to be able to load certain GHC modules in interpreted mode in > ghci so I can set breakpoints in them. I have tests in the testsuite > that are compiled by inplace/bin/ghc-stage2 with -package ghc. I can > load the tests with ghc-stage2

Re: Debugging GHC with GHCi

2017-01-08 Thread Richard Eisenberg
> On Jan 8, 2017, at 8:33 PM, Thomas Jakway wrote: > > Currently I'm using trace & friends to do printf-style debugging but it's > definitely not ideal. I don't have an answer to your question, but I can tell you that this is exactly what I do. It's not ideal at all. If you

Phabricator upgrade underway

2017-01-08 Thread Ben Gamari
Hello everyone, I'll be bringing down Phabricator for an upgrade in a few minutes. I'll let you know when things are back up. Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org

Re: nofib on Shake

2017-01-08 Thread Joachim Breitner
Hi, Am Sonntag, den 08.01.2017, 13:45 -0500 schrieb Ben Gamari: > > We could also create a cabal and stack files for `nofib-analyse` (making > > it possible to use some libraries for it). > > > This would be great. This would allow me to drop a submodule from my own > performance monitoring tool.

Re: nofib on Shake

2017-01-08 Thread Ben Gamari
Michal Terepeta writes: > Hi all, > > While looking at nofib, I've found a blog post from Neil Mitchell [1], > which describes a Shake build system for nofib. The comments mentioned > that this should get merged, but it seems that nothing actually happened? > Is there

nofib on Shake

2017-01-08 Thread Michal Terepeta
Hi all, While looking at nofib, I've found a blog post from Neil Mitchell [1], which describes a Shake build system for nofib. The comments mentioned that this should get merged, but it seems that nothing actually happened? Is there some fundamental reason for that? If not, I'd be interested

Re: Trac to Phabricator (Maniphest) migration prototype

2017-01-08 Thread Richard Eisenberg
> On Jan 8, 2017, at 12:40 AM, Ben Gamari wrote: > > * Metadata: Custom fields are supported. In agreement with your comments above, I'm glad to see this. Trac's metadata currently is suboptimal, but I don't think this means we should throw out the ability to have