Re: GHC release timing and future build infrastructure

Glad I could provide some useful thoughts! > You are to some extent correct; an unwillingness to release before major > (for some definition of "major") bugs are fixed will inevitably lead to > slips. However, I think a faster release cycle will make it easier to > accept releases with such bugs

Re: GHC release timing and future build infrastructure

nightly release. On Thu, Aug 3, 2017 at 9:38 AM, Herbert Valerio Riedel <hvrie...@gmail.com> wrote: > Hi! > > On 2017-08-03 at 08:41:59 +0200, Ara Adkins wrote: > > [...] > > > I nevertheless see `stack` as a huge boon for easing adoption of new > > compi

Re: GHC release timing and future build infrastructure

Heya, I very much agree with the thoughts on the variability of the release cadence. The following is somewhat of a stream of consciousness as I read, so please excuse any lack of coherence. When you talk about the bugs being significant blockers to the latest release I feel like that kind

Re: Alex install failure

NFS can be pretty dodgy with transient files due to latency. Sometimes the delete takes appreciable time after the command is issued so the lock file might just be persisting. I’d try installing into a cabal sandbox on a local drive and see if the same issue crops up. _ara > On 18 Aug 2017,

Re: Alex install failure

Aug 2017, at 00:37, Simon Peyton Jones <simo...@microsoft.com> wrote: > > Maybe so, but it's really not a good experience for GHC/Cabal users. If > aptget did this, people would bleat loudly. > > Simon > > | -Original Message- > | From: Ara Adkins [mailto:m...

Re: A type checker plugin for row types

Excellent! I've very much been looking forward to having a look at the code for this! On Sat, Sep 16, 2017 at 10:27 PM, Nicolas Frisby wrote: > I've uploaded the code to GitHub. > > https://github.com/nfrisby/coxswain > > I went with a BSD3 licence. > > It's still very

Re: dll-split

for compiling ghc we don't have to include it in the bindist > so license would be less of an issue I think. > > I'll modify the scripts to pull it automatically when I submit the rest of > the patches. > > Thanks, > Tamar > >> On Wed, Aug 30, 2017 at 3:25 PM

Re: A type checker plugin for row types

Just given this a read! It looks like you’ve put a fantastic amount of effort into this so far, and I can certainly see how it’s finding its legs! I’m very much looking forward to seeing this develop further. I can definitely foresee some uses for polykinded column types, and the possibility

Re: A type checker plugin for row types

! Definitely a useful addition to the wiki page. _ara > On 10 Sep 2017, at 23:58, Nicolas Frisby <nicolas.fri...@gmail.com> wrote: > > Whoops! I forgot about that section of my draft. I added a little blurb > ("Performance?") Thanks Ara! > > > >> On

Re: Review of CONTRIBUTORS.md

Hey Ben, Looks good to me for the most part! I think that you should include a link to the Newcomers page [1] as a whole, even though it has some overlap with the quick start guide and you’ve included a link to the ‘Finding a Ticket’ subsection therein. I also think that a few more pointers

Re: Review of CONTRIBUTORS.md

my phone! _ara > On 28 Sep 2017, at 01:33, Ben Gamari <b...@well-typed.com> wrote: > > Ara Adkins <m...@ara.io> writes: > >> Hey Ben, >> >> Looks good to me for the most part! I think that you should include a >> link to the Newcomers page

Re: GHC staus

I’m definitely interested in hearing more about cross compilation for iOS. Might actually make an idea I’ve had brewing into something feasible! _ara > On 4 Sep 2017, at 11:16, Manuel M T Chakravarty wrote: > > +1 for a lighting talk on that! (You can tell the

Re: dll-split

With a hit like that I think it should at least be highly publicised that it can cause huge hits to compilation time. I would support bundling the executable if it has a compatible license. _ara On Wed, Aug 30, 2017 at 3:19 PM, Ryan Scott wrote: > Thanks for putting so

Re: A newcomer: how to start

Hey Sergey, I’d honestly head straight for the GHC newcomers guide [0]! Once you’re familiar with all of that just head for Trac and look for the low hanging fruit tasks! Most importantly, don’t forget to ask questions! Nobody here bites! Best, _ara [0]

Re: Commit Notifications Flood

them too ☹ > > > > *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of *Ara > Adkins > *Sent:* 20 November 2017 21:07 > *To:* GHC developers <ghc-devs@haskell.org> > *Subject:* Commit Notifications Flood > > > > Is anyone else getting an absolute floo

Commit Notifications Flood

Is anyone else getting an absolute flood of commit emails related to haddock? I remember this happening a little while back with the hadrian merge into the GHC tree. Best, _ara ___ ghc-devs mailing list ghc-devs@haskell.org

Re: Moving hadrian to submodule

Sounds good! Hopefully this doesn’t cause a flood of commit messages. _ara > On 8 Dec 2017, at 18:50, Ben Gamari wrote: > > Hello everyone, > > A bit over a month ago we merged hadrian into the ghc tree as a subtree. > Unfortunately, those working on Hadrian have found

Re: [commit: ghc] wip/nfs-locking: Use conventional whitespacing for @. (31515fa)

It’s been one heck of a day with these coming in. It does seem to have stopped now. _ara > On 27 Oct 2017, at 22:58, Simon Peyton Jones via ghc-devs > wrote: > > yes I think it's stopped. I'' remove my junk-mail rule > > | -Original Message- > | From: Ben

Re: Failure to Build

Hi Ben, That was spot on! I guess there's something wrong with the stack install of happy - using the one installed from the system package manager worked perfectly. Best, _ara On Tue, 31 Jul 2018 at 16:56, Ben Gamari wrote: > Ara Adkins writes: > > > Thanks all for the in

Failure to Build

Hey Devs, I'm having trouble building the head of the ghc-8.6 branch (`26a7f850d1`) on my Arch Linux machine. The essence of the error is this as follows, though the full result of make (to the point of error) is attached. ``` Configuring template-haskell-2.14.0.0... ghc-cabal: Encountered

Re: Failure to Build

Thanks all for the insight so far! Doing that has got me further along in the build, but it is still failing. Amongst the output of `make` it seems that the offending error is as follows: ``` happy:

Using GHC Core as a Language Target

Hey All, I was chatting to SPJ about the possibility of using GHC Core + the rest of the GHC compilation pipeline as a target for a functional language, and he mentioned that asking here would likely be more productive when it comes to the GHC API. I'm wondering where the best place would be for

Re: Using GHC Core as a Language Target

> Dive into GHC: Intermediate Forms > Dive into GHC: Targeting Core > Cheers, > Csaba Hruska > >> On Thu, Oct 25, 2018 at 8:51 PM Ara Adkins wrote: >> Heya, >> >> Those are exactly the kind of pointers I was hoping for. Thanks Iavor. >> >> I’m sure I’ll ha

Re: Using GHC Core as a Language Target

> core syntax. > > 3. The "desugarer" (in `compiler/deSugar`) is the GHC phase that translates > the front end syntax (hsSyn) into core, so that should have lots of examples > of how to generate core. > > Cheers, > -Iavor > > > > >

Re: [GHC DevOps Group] The future of Phabricator

Also as part of the silent bystander group, I would definitely be okay with a swap to GitLab. I don’t have anything particularly against Phab and Trac, but I recognise the reduction in general friction the swap would create. _ara > On 3 Nov 2018, at 13:38, Richard Eisenberg wrote: > > >

Re: Welcome to GitLab!

Thanks ben! Great to know. CC the list in case anyone else was interested. _ara > On 27 Dec 2018, at 15:06, Ben Gamari wrote: > > Ara Adkins writes: > >> Along the lines of things needing to be adapted, are we moving the >> ghc-commits mailing list over to GL? >&

GitLab Migration

Hey All, Sorry for my confusion, but I'm a bit unclear as to when we're meant to start working against the GHC repo on the gitlab.haskell.org instance. I had in mind that the cutover was intended to be the 18th, but going on there it still appears as if it's mirrored from git.haskell.org. Can

Re: GitLab Migration

is to redirect the github mirror > (https://github.com/ghc/ghc), too. > > Cheers, > >Gabor > >> On 12/20/18, Ara Adkins wrote: >> Hey All, >> >> Sorry for my confusion, but I'm a bit unclear as to when we're meant to >> start working

Re: Welcome to GitLab!

? Should pull requests be blocked on the > former? > > Anyway some readmes need to be adapted for the new world order. > > Cheers, > >Gabor > >> On 12/27/18, Ara Adkins wrote: >> Congrats to Ben and everybody involved! This has been a long time comin

Re: GitLab Migration

Perfect. Thanks for the clarification Ben! _ara > On 21 Dec 2018, at 16:55, Ben Gamari wrote: > > Ara Adkins writes: > >> Hey All, >> >> Sorry for my confusion, but I'm a bit unclear as to when we're meant to >> start working against the GHC repo on the g

The GHC Proposals Process

Hey All, Now we have our own git instance in GitLab, are there any plans to move the proposals process from GitHub? _ara ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: The GHC Proposals Process

I certainly have no compelling reasons to do so! It was more a question than anything else, as I happen to agree that the reach of GitHub is beneficial in this case! _ara > On 4 Jan 2019, at 18:56, Ben Gamari wrote: > >> On January 4, 2019 12:56:58 PM EST, Ara Adkins wrote

The Trac Wiki and the GitLab Migration

Hey All, I’ve been doing a decent amount of thinking about the GitLab migration and realised that I’d not seen any discussion of what we plan to do with all the information in the Trac Wiki. If there has been some and I’ve missed it I apologise. In essence, I’m wondering what the current plan

Re: The Trac Wiki and the GitLab Migration

Brilliant. Thanks Ben and Brandon for the quick responses. Ben, if there’s any way I can help wit that migration, even to the point of manual cleanup, do let me know! _ara > On 28 Dec 2018, at 20:13, Ben Gamari wrote: > > Ara Adkins writes: > >> Hey All, >> >

Merge Request Submission Confusion

Hey all, I'm trying to submit a minor MR as described on the wiki [0]. I can't seem to find the mentioned 'New Merge Request' button, however. Do I need a specific set of permissions to open MRs? Any pointers would be appreciated. Best, _ara [0]

Re: Merge Request Submission Confusion

I don't, which is the curious thing. There's just a gap above the filter dropdown where it should be. On Mon, 8 Apr 2019 at 13:56, Ben Gamari wrote: > > Ara Adkins writes: > > > Hey all, > > > > I'm trying to submit a minor MR as described on the wiki [0]. I can't >

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

all the time. _ara > On 6 Mar 2019, at 11:21, Ben Gamari wrote: > > > >> On March 6, 2019 6:11:49 AM EST, Ara Adkins wrote: >> Super excited for this! Thank you to everyone whose put in so much hard >> work to get it done! >> >> One question: what

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

should achieve the same thing as the mailing > list did? > > > > On Wed, Mar 6, 2019 at 12:00 PM Sylvain Henry wrote: > >> I use it to track tickets and I would also like to see it continued. >> >> Sylvain >> >> On 06/03/2019 12:33, Ara Adkins wrote: >&g

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

Super excited for this! Thank you to everyone whose put in so much hard work to get it done! One question: what is happening with the trac tickets mailing list? I imagine it’ll be going away, but for those of us that use it to keep track of things is there a recommended alternative? Best,

Re: [Haskell-cafe] Final steps in GHC's Trac-to-GitLab migration

I think that's a reliable replacement for the ghc-tickets mailing list if it works well. I'll have to see once the cut-over happens! On Wed, 6 Mar 2019 at 16:44, Ben Gamari wrote: > Ara Adkins writes: > > > That would be perfect if so. I couldn't find a way to do it when I looked

Re: Trac to GitLab migration underway

Thanks for all the hard work to all involved! I’m very excited for everything to be in one place! _ara > On 10 Mar 2019, at 22:15, Shayne Fletcher via ghc-devs > wrote: > > > >> On Sun, Mar 10, 2019 at 5:38 PM Ben Gamari wrote: >> Ben Gamari writes: >> >> > Hello everyone, >> > >> > I

Re: Gitlab Email Broken (again)

The same thing seems to have happened to me too. _ara > On 13 Mar 2019, at 07:39, Matthew Pickering > wrote: > > HI Ben, > > I am not receiving emails from gitlab again. Is there a way we can > make email more robust? > > Matt > ___ > ghc-devs

Marge Bot Permissions on Trac

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 ___ ghc-devs mailing list ghc-devs@haskell.org

Re: Merge Request Submission Confusion

ursion/ghc On Mon, 8 Apr 2019 at 19:22, Ben Gamari wrote: > > Ara Adkins writes: > > > I don't, which is the curious thing. There's just a gap above the > > filter dropdown where it should be. > > > Hmm, it's possible this is related to the fact that you had onl

Re: Merge Request Submission Confusion

Perhaps the current 'my fork is not available' mess is actually the root cause, then? On Mon, 8 Apr 2019 at 21:56, Artem Pelenitsyn wrote: > > On Mon, 8 Apr 2019 at 14:22 Ben Gamari wrote: >> >> Ara Adkins writes: >> >> > I don't, which is the curiou

Re: Marge bot UX improvement suggestion

Yeah I just got a flood of a few hundred emails from ‘Moe Bot’. _ara > On 26 Apr 2019, at 10:41, Phyx wrote: > > Speaking of bots.. What's a Moe bot? Haha. > > Sent from my Mobile > >> On Thu, Apr 25, 2019, 16:06 Ben Gamari wrote: >> Ömer Sinan Ağacan writes: >> >> > I think it'd be

Re: Moe Bot

Hey David, This is going to be a great boon! Thanks so much for your hard work on this! _ara > On 26 Apr 2019, at 11:16, David Eichmann wrote: > > Hello All, > > I've been working on Moe Bot recently who will quote commits that mention > issues. When a commit is pushed to master, Moe will