Hi Arash, Thanks for your reply. I'm interested in stepping through the compiler part (Lexer, Parser, etc...) of GHC for now. Thanks for the link to the commentary. I'm going through it right now. ------- "Hi Omar, You might want to narrow your scope to one part of GHC. For example, I mostly focused on the Run Time System to be able to conduct my master's thesis. Also, you might want to start off with a tiny goal, like to fix bug XYZ. Oh, and most important of all is the Commentary, which I think of as a wiki for GHC developers. http://ghc.haskell.org/trac/ghc/wiki/Commentary Cheers, Arash" Omar Mefire, Le Mardi 7 octobre 2014 0h08, Omar Mefire a écrit : Hi Arash, Thanks for your reply. I'm interested in stepping through the compiler part (Lexer, Parser, etc...) of GHC for a beginning. Thanks for the link to the commentary. I'm going through it right now. P.S: I emailed you directly because I had some difficulties figuring out how to respond only to your message instead of the whole daily digest. Hopefully, will figure it out shortly. :) " Hi Omar, You might want to narrow your scope to one part of GHC. For example, I mostly focused on the Run Time System to be able to conduct my master's thesis. Also, you might want to start off with a tiny goal, like to fix bug XYZ. Oh, and most important of all is the Commentary, which I think of as a wiki for GHC developers. http://ghc.haskell.org/trac/ghc/wiki/Commentary" Omar Mefire, Le Lundi 6 octobre 2014 12h55, "ghc-devs-request@haskell.org" a écrit : Send ghc-devs mailing list submissions to ghc-devs@haskell.org To subscribe or unsubscribe via the World Wide Web, visit http://www.haskell.org/mailman/listinfo/ghc-devs or, via email, send a message with subject or body 'help' to ghc-devs-request@haskell.org You can reach the person managing the list at ghc-devs-owner@haskell.org When replying, please edit your Subject line so it is more specific than "Re: Contents of ghc-devs digest..." Today's Topics: 1. Re: GitHub pull requests (Richard Eisenberg) 2. RE: Show instance for SrcSpan (Simon Peyton Jones) 3. Re: GitHub pull requests (Ben Gamari) 4. Re: Stepping through ghc (Arash Rouhani) 5. RE: Again: Uniques in GHC (p.k.f.holzenspies@utwente.nl) ---------------------------------------------------------------------- Message: 1 Date: Mon, 6 Oct 2014 10:32:23 -0400 From: Richard Eisenberg To: andreas.abel@gu.se Cc: "ghc-devs@haskell.org Devs" Subject: Re: GitHub pull requests Message-ID: Content-Type: text/plain; charset=us-ascii I think the "arc" barrier is significant. Personally, while I feel quite comfortable hacking on Haskell code, system tools are always a bit of a mystery. Those of you who help manage the infrastructure may feel like the tools are easy enough to pick up, but I'm sure there are many competent Haskell programmers out there who dread learning new tooling. (Perhaps I'm a representative sample of this set. I still say `git help merge` before just about every merge, just to make sure that I'm remembering the concepts correctly.) I absolutely believe that we should use the best tools available and that committed GHC contributors should have to learn these tools as necessary. Though I've had my problems with Phab and `arc`, I'm confident that this tool was chosen after a deliberative process and am grateful that we have leaders in this area in our midst. All that said, I think that the suggestion just to accept GitHub pull requests will lead to confusion, if only for the namespace problem. If we start to accept pull requests, then we are de facto going to have to deal with both the GH issue tracker and Trac's (and Phab's), and that is a terrible place to be. Part of the automated response to pull request submissions could be a post on the GH pull request record pointing folks to the Phab review that was created in response. The pull request would then be closed. I agree with the comment that users will be more committed to learn Phab once they have contributed. That's why I wanted to point them to Phab in the automated response to the GH pull request. I think there's a psychological commitment made by a person once they click "submit pull request" and they will be happy enough to follow up on Phab, especially if commenting and such doesn't require the installation of a local tool. Richard ------------------------------ Message: 2 Date: Mon, 6 Oct 2014 18:10:37 +0000 From: Simon Peyton Jones To: Alan & Kim Zimmerman , "ghc-devs@haskell.org" Subject: RE: Show instance for SrcSpan Message-ID: <618BE556AADD624C9C918AA5D5911BEF3F319EA3@DB3PRD3001MB020.064d.mgd.msft.net> Content-Type: text/plain; charset="utf-8" By all means do so S From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Alan & Kim Zimmerman Sent: 06 October 2014 13:59 To: ghc-devs@haskell.org Subject: Show instance for SrcSpan Is there any reason I can't put in a diff request to replace the derived Show instance for SrcSpan with a handcrafted one that does not exhausively list the constructors, making it more readable? Alan