- ghc-devs - Haskell.org

Newcomers' Guide to GHC Development
by Tobias Dammers 13 Mar '19

13 Mar '19

Dear all, With the migration of our affairs from Trac to GitLab nearing completion, I would like to ask for a final round of feedback on the new Newcomers' Guide to GHC development. The draft can be found here: https://github.com/tdammers/ghc-wiki/blob/wip/newcomers/newcomers-tutorial.… TL;DR: If you have any kind of input / critique / praise regarding this document, feel free to reply, or, even better, issue a PR on github. Some background: The purpose of this document is to provide potential contributors with a practical, no-nonsense tutorial, guiding them from "I know nothing about GHC development" to their first successful merge request. The document has been compiled using existing wiki content, revised and edited to match the current state of affairs (particularly using Hadrian as the recommended build system), and to tune it to the target audience of first-time contributors. As such, we avoid going off on tangents (e.g., we do not explain how to use the make-based alternative build system), and we only explain what you need to understand in order to get going (e.g., we do not provide a complete run-down of all hadrian options). A few nonlinearities were deemed necessary in order to make the tutorial suitable across target platforms; Windows in particular requires some special attention. Other than that, however, we try to provide as linear an experience as we reasonably can. So with that said; all feedback and suggestions on this are welcome. We have gotten some great responses already, but I'd like to gather one more round of feedback before merging it into the freshly-migrated Haskell Wiki on GitLab. Thank you for your attention! -- Tobias Dammers - tdammers(a)gmail.com

5 6

From tickets to merge requests and vice versa
by Simon Peyton Jones 12 Mar '19

12 Mar '19

Ben, Matthew I wrote up notes on how to get from MR to issue, and from issue to MR, in my help page: https://gitlab.haskell.org/ghc/ghc/wikis/working-conventions/git-lab-spj (See "Issues" and "Merge requests" headings) Alas, it seems that I was lying * Issue #16411 does not have a "relevant merge request" link to MR!520, even though the latter plainly mentions the former. That seems deeply strange, and makes it hard to see if the issue has a MR, let alone which one it is. * Somehow MR!520 says "closes #16411" rather than just "mentions #16411". Perhaps this is good, but how did it know to do that? Simon

3 2

Marge Bot Permissions on Trac
by Ara Adkins 12 Mar '19

12 Mar '19

Hey all, though mostly hey Ben, Just figured I should let you know that marge still seems to be making changes to trac tickets as of about four hours ago when sending this email. Best, _ara

1 0

Search on gitlab
by Simon Peyton Jones 12 Mar '19

12 Mar '19

I searched for captureTopConstraints on GitLab, using the search box at the top. But it found nothing. And yet here it is https://gitlab.haskell.org/ghc/ghc/merge_requests/508 What am I doing wrong? Thanks Simon

3 3

New and improved ghc-in-ghci target
by Matthew Pickering 12 Mar '19

12 Mar '19

Hi all, My patch to improve the ghc-in-ghci target just got merged a few minutes ago. Now from a clean tree it only takes a few minutes to launch the target. You can now load ghc into ghci by running the following script: ./hadrian/ghci.sh https://gitlab.haskell.org/ghc/ghc/tree/master/hadrian#fast-feedback-using-… Please try it out and open tickets if there are any issues on your system. Matt

2 1

Trac to GitLab migration underway
by Ben Gamari 12 Mar '19

12 Mar '19

Hello everyone, I have started the process of migrating GHC's Trac content to GitLab. GitLab (gitlab.haskell.org) and Trac (ghc.haskell.org) will be down until this process has finished. I will post updates as necessary. However, if you do need to refer to a ticket, you are welcome to use the staging server [1], which has a reasonably up-to-date (read-only) snapshot of our Trac tickets. However, do note that unfortunately authentication via GitHub will not work on this site. Cheers, - Ben [1] https://gitlab.staging.haskell.org/

10 18

git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work
by Shayne Fletcher 10 Mar '19

10 Mar '19

I appreciate this isn't really "our" problem :) Nonetheless, if there's any config we can do on the repo on gitlab, that would be cool. Other URLs (like github) for example are fine - something specific to gitlab. -- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html <http://www.digitalasset.com/emaildisclaimer.html>. If you are not the intended recipient, please delete this message.

5 11

Why can't we re-install the template-haskell package?
by Moritz Angermann 08 Mar '19

08 Mar '19

Dear friends, as I'm working on making lib:ghc re-installable [1][2]. Ideally I'd prefer we only had to freeze rts + ghc-prim and maybe base (which would implicate the integer library). However, we apparently can't re-install Template Haskell I'm told. Not just not upgrade it, but not even re-install it (same version). I've attached some rough dependency graph (which I hope is correct for ghc 8.8). Fixing template-haskell implies ghc-boot-th, pretty, deepseq and array. Can someone shed some light onto the details here? What are the fundamental issues we can't reinstall template-haskell? Cheers, Moritz -- [1]: https://gitlab.haskell.org/ghc/ghc/merge_requests/490 [2]: https://gitlab.haskell.org/ghc/ghc/merge_requests/506

4 4

git.haskell.org is broken
by Shayne Fletcher 08 Mar '19

08 Mar '19

As of today, git clone git://git.haskell.org/ghc.git --recursive is failing with, error: Server does not allow request for unadvertised object 94855814e2e4f7a0f191ffa5b4c98ee0147e3174 Fetched in submodule path 'libraries/binary', but it did not contain 94855814e2e4f7a0f191ffa5b4c98ee0147e3174. Direct fetching of that commit failed. -- Shayne Fletcher Language Engineer c: +1 917 699 7763 e: shayne.fletcher(a)daml.com Digital Asset Holdings, LLC 4 World Trade Center 150 Greenwich Street, 47th Floor <https://maps.google.com/?q=150+Greenwich+Street,+47th+Floor%C2%A0+%C2%A0+%C…> New York, NY 10007, USA <https://maps.google.com/?q=150+Greenwich+Street,+47th+Floor%C2%A0+%C2%A0+%C…> digitalasset.com <http://www.digitalasset.com/> -- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html <http://www.digitalasset.com/emaildisclaimer.html>. If you are not the intended recipient, please delete this message.

3 3

Re: Why can't we re-install the template-haskell package?
by Ryan Scott 07 Mar '19

07 Mar '19

My (limited) understanding is that template-haskell is not reinstallable for the same reasons that base and ghc-prim aren't reinstallable: the GHC codebase directly wires in several definitions several functions, types, and data constructors from template-haskell. See THNames [1]. If one were to, say, use GHC 8.6 but install a different version of template-haskell than the one that came bundled with 8.6, then it's almost certain that lots of code in THNames would no longer work, since they could be referencing identifiers that no longer exist (if the new version of template-haskell doesn't have them). Ryan S. ----- [1] https://gitlab.haskell.org/ghc/ghc/blob/25c3dd39f7d446f66b5c967be81f80cd7fa…

1 0