From mail at joachim-breitner.de Fri Sep 7 19:54:34 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Fri, 07 Sep 2018 21:54:34 +0200 Subject: [ghc-steering-committee] Please Review: Show Types as Symbols (#164), Shepherd: Richard Eisenberg Message-ID: <076c8de4d3619c45139494cdb61f7c9fb50c579a.camel@joachim-breitner.de> Dear Committee, this is your secretary speaking: Provide a primitive to show types as Symbols, by Sandy Maguirer, was proposed https://github.com/ghc-proposals/ghc-proposals/pull/164 I propose Richard as the shepherd, he already showed interest in this proposal. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From marlowsd at gmail.com Mon Sep 10 07:13:21 2018 From: marlowsd at gmail.com (Simon Marlow) Date: Mon, 10 Sep 2018 08:13:21 +0100 Subject: [ghc-steering-committee] StableName guarantee (#163), recommendation: accept Message-ID: The proposer wants to change the implementation of StableNames, and noticed that the existing implementation has the property that, for two StableNames s1 and s2 that are currently live, hashStableName s1 == hashStableName s2 ==> s1 == s2 this property is not documented. As far as we know, there isn't any code in the wild that relies on it. In fact, relying on it would be tricky due to the requirement that s1 and s2 have to be live - as soon as a StableName becomes unreachable from the GC's point of view, the index into the table that is used to provide the result of hashStableName is reused. The proposal is to remove this property. Well, a future refactoring of the StableName implemnetation would actually remove the property, the proposer wants the committee to consider whether the property in question is worth keeping (and therefore documenting). I think it's pretty clear that we don't want to document this property, because in order to do so we would have to give a precise definition of what "live" means, which is not possible. Furthermore, we don't know of any use cases in the wild. So, let's accept the proposal. Cheers Simon -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at joachim-breitner.de Mon Sep 10 07:45:18 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Mon, 10 Sep 2018 09:45:18 +0200 Subject: [ghc-steering-committee] StableName guarantee (#163), recommendation: accept In-Reply-To: References: Message-ID: <2441e076867c5e8ed40f4f0e572c2b718cccff42.camel@joachim-breitner.de> SGTM (sounds good to me) I like the easy ones :-) Am Montag, den 10.09.2018, 08:13 +0100 schrieb Simon Marlow: > The proposer wants to change the implementation of StableNames, and noticed that the existing implementation has the property that, for two StableNames s1 and s2 that are currently live, > > hashStableName s1 == hashStableName s2 ==> s1 == s2 > > this property is not documented. As far as we know, there isn't any code in the wild that relies on it. In fact, relying on it would be tricky due to the requirement that s1 and s2 have to be live - as soon as a StableName becomes unreachable from the GC's point of view, the index into the table that is used to provide the result of hashStableName is reused. > > The proposal is to remove this property. Well, a future refactoring of the StableName implemnetation would actually remove the property, the proposer wants the committee to consider whether the property in question is worth keeping (and therefore documenting). > > I think it's pretty clear that we don't want to document this property, because in order to do so we would have to give a precise definition of what "live" means, which is not possible. Furthermore, we don't know of any use cases in the wild. So, let's accept the proposal. > > Cheers > Simon > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From eric at seidel.io Tue Sep 11 13:25:51 2018 From: eric at seidel.io (Eric Seidel) Date: Tue, 11 Sep 2018 09:25:51 -0400 Subject: [ghc-steering-committee] Proposal: Define Kinds Without Promotion (#106) In-Reply-To: References: <1534293119.3992207.1474414112.3E640798@webmail.messagingengine.com> <1534463249.3187033.1476814616.5C5C1219@webmail.messagingengine.com> <66BAC73A-6A24-4652-B00E-F4237B5DF447@cs.brynmawr.edu> <859D625D-5E9F-4221-8438-CA9F22F31D59@cs.brynmawr.edu> <1534857494.2034461.1481235360.7051A7E7@webmail.messagingengine.com> <1535549236.2892749.1490033464.30E49ABA@webmail.messagingengine.com> <1535563296.655366.1490329456.452DC380@webmail.messagingengine.com> <1535563339.655508.1490330888.63E98E2B@webmail.messagingengine.com> <1535575369.710652.1490551880.0DEFABF2@webmail.messagingengine.com> Message-ID: <1536672351.1279264.1504213136.2C38EA27@webmail.messagingengine.com> The proposal has been updated to specify that record selectors, quantifiers, and bangs/unpacks are disallowed in `type data`. These restrictions all make sense to me, at least for now, so I think we can properly declare this proposal accepted. On Thu, Aug 30, 2018, at 09:53, Iavor Diatchki wrote: > Indeed, record selectors are not supported in type data, and should result > in an error. Same for other special things like strictness annotations, > unpack pragmas, and quantifiers. > > I am on vacation without a computer at the moment and I am not sure if I > can edit the proposal from my phone, but I'll give it a go later. > > Iavor > > On Wed, Aug 29, 2018, 11:42 PM Eric Seidel wrote: > > > Yes, I got a bit excited to exercise my power :) > > > > On Wed, Aug 29, 2018, at 15:11, Joachim Breitner wrote: > > > Hi, > > > > > > in that case, I suggest you work with the authors to get that fixed, > > > and only then pronounce it accepted :-) > > > > > > Cheers, > > > Joachim > > > > > > > > > > > > Am Mittwoch, den 29.08.2018, 13:22 -0400 schrieb Eric Seidel: > > > > Though I'd still like to have it specify what happens with record > > selectors, as pointed out by Adam. > > > > > > > > On Wed, Aug 29, 2018, at 13:21, Eric Seidel wrote: > > > > > Ok, then I declare it accepted! > > > > > > > > > > On Wed, Aug 29, 2018, at 13:17, Joachim Breitner wrote: > > > > > > Hi, > > > > > > > > > > > > Am Mittwoch, den 29.08.2018, 09:27 -0400 schrieb Eric Seidel: > > > > > > > What's the next step, Joachim? Do I just mark the proposal as > > accepted? > > > > > > > > > > > > yes. Or you declare it as accepted here on the mailing list, and I > > mark > > > > > > it as such on GitHub (I have to touch it anyways, to merge it and > > give > > > > > > it the final proposal number). > > > > > > > > > > > > Cheers, > > > > > > Joachim > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Joachim Breitner > > > > > > mail at joachim-breitner.de > > > > > > http://www.joachim-breitner.de/ > > > > > > _______________________________________________ > > > > > > ghc-steering-committee mailing list > > > > > > ghc-steering-committee at haskell.org > > > > > > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > > > > Email had 1 attachment: > > > > > > + signature.asc > > > > > > 1k (application/pgp-signature) > > > > > > > > _______________________________________________ > > > > ghc-steering-committee mailing list > > > > ghc-steering-committee at haskell.org > > > > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > -- > > > Joachim Breitner > > > mail at joachim-breitner.de > > > http://www.joachim-breitner.de/ > > > _______________________________________________ > > > ghc-steering-committee mailing list > > > ghc-steering-committee at haskell.org > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > Email had 1 attachment: > > > + signature.asc > > > 1k (application/pgp-signature) > > _______________________________________________ > > ghc-steering-committee mailing list > > ghc-steering-committee at haskell.org > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > From bravit111 at gmail.com Wed Sep 12 02:14:41 2018 From: bravit111 at gmail.com (Vitaly Bragilevsky) Date: Tue, 11 Sep 2018 19:14:41 -0700 Subject: [ghc-steering-committee] Proposal: Lazy unboxed tuples / warn on unbanged strict patterns (#35); Recommendation, attempt 2: Accept In-Reply-To: References: Message-ID: Hi all, The proposal "Lazy unboxed tuples / warn on unbanged strict patterns (#35)" (https://github.com/ghc-proposals/ghc-proposals/pull/35) is officially accepted since no complains received. Joachim, could you please label it as accepted on GitHub and do whatever should be done there? Regards, Vitaly On Fri, Aug 24, 2018 at 5:11 PM Vitaly Bragilevsky wrote: > Hi, > > This is my revised recommendation for the lazy unboxed tuples proposal ( > https://github.com/ghc-proposals/ghc-proposals/pull/35). It is already > implemented, and I don't see strong opposition to it, so my recommendation > is ACCEPT. > > Silence is understood as agreement. > > Regards, > Vitaly > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at joachim-breitner.de Wed Sep 12 06:52:22 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Wed, 12 Sep 2018 08:52:22 +0200 Subject: [ghc-steering-committee] Proposal: Define Kinds Without Promotion (#106) In-Reply-To: <1536672351.1279264.1504213136.2C38EA27@webmail.messagingengine.com> References: <1534293119.3992207.1474414112.3E640798@webmail.messagingengine.com> <1534463249.3187033.1476814616.5C5C1219@webmail.messagingengine.com> <66BAC73A-6A24-4652-B00E-F4237B5DF447@cs.brynmawr.edu> <859D625D-5E9F-4221-8438-CA9F22F31D59@cs.brynmawr.edu> <1534857494.2034461.1481235360.7051A7E7@webmail.messagingengine.com> <1535549236.2892749.1490033464.30E49ABA@webmail.messagingengine.com> <1535563296.655366.1490329456.452DC380@webmail.messagingengine.com> <1535563339.655508.1490330888.63E98E2B@webmail.messagingengine.com> <1535575369.710652.1490551880.0DEFABF2@webmail.messagingengine.com> <1536672351.1279264.1504213136.2C38EA27@webmail.messagingengine.com> Message-ID: Merged! Am Dienstag, den 11.09.2018, 09:25 -0400 schrieb Eric Seidel: > The proposal has been updated to specify that record selectors, quantifiers, and bangs/unpacks are disallowed in `type data`. These restrictions all make sense to me, at least for now, so I think we can properly declare this proposal accepted. > > On Thu, Aug 30, 2018, at 09:53, Iavor Diatchki wrote: > > Indeed, record selectors are not supported in type data, and should result > > in an error. Same for other special things like strictness annotations, > > unpack pragmas, and quantifiers. > > > > I am on vacation without a computer at the moment and I am not sure if I > > can edit the proposal from my phone, but I'll give it a go later. > > > > Iavor > > > > On Wed, Aug 29, 2018, 11:42 PM Eric Seidel wrote: > > > > > Yes, I got a bit excited to exercise my power :) > > > > > > On Wed, Aug 29, 2018, at 15:11, Joachim Breitner wrote: > > > > Hi, > > > > > > > > in that case, I suggest you work with the authors to get that fixed, > > > > and only then pronounce it accepted :-) > > > > > > > > Cheers, > > > > Joachim > > > > > > > > > > > > > > > > Am Mittwoch, den 29.08.2018, 13:22 -0400 schrieb Eric Seidel: > > > > > Though I'd still like to have it specify what happens with record > > > > > > selectors, as pointed out by Adam. > > > > > > > > > > On Wed, Aug 29, 2018, at 13:21, Eric Seidel wrote: > > > > > > Ok, then I declare it accepted! > > > > > > > > > > > > On Wed, Aug 29, 2018, at 13:17, Joachim Breitner wrote: > > > > > > > Hi, > > > > > > > > > > > > > > Am Mittwoch, den 29.08.2018, 09:27 -0400 schrieb Eric Seidel: > > > > > > > > What's the next step, Joachim? Do I just mark the proposal as > > > > > > accepted? > > > > > > > > > > > > > > yes. Or you declare it as accepted here on the mailing list, and I > > > > > > mark > > > > > > > it as such on GitHub (I have to touch it anyways, to merge it and > > > > > > give > > > > > > > it the final proposal number). > > > > > > > > > > > > > > Cheers, > > > > > > > Joachim > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Joachim Breitner > > > > > > > mail at joachim-breitner.de > > > > > > > http://www.joachim-breitner.de/ > > > > > > > _______________________________________________ > > > > > > > ghc-steering-committee mailing list > > > > > > > ghc-steering-committee at haskell.org > > > > > > > > > > > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > > > > > Email had 1 attachment: > > > > > > > + signature.asc > > > > > > > 1k (application/pgp-signature) > > > > > > > > > > _______________________________________________ > > > > > ghc-steering-committee mailing list > > > > > ghc-steering-committee at haskell.org > > > > > > > > > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > > -- > > > > Joachim Breitner > > > > mail at joachim-breitner.de > > > > http://www.joachim-breitner.de/ > > > > _______________________________________________ > > > > ghc-steering-committee mailing list > > > > ghc-steering-committee at haskell.org > > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > > Email had 1 attachment: > > > > + signature.asc > > > > 1k (application/pgp-signature) > > > > > > _______________________________________________ > > > ghc-steering-committee mailing list > > > ghc-steering-committee at haskell.org > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > > > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From mail at joachim-breitner.de Wed Sep 12 06:52:31 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Wed, 12 Sep 2018 08:52:31 +0200 Subject: [ghc-steering-committee] Proposal: Lazy unboxed tuples / warn on unbanged strict patterns (#35); Recommendation, attempt 2: Accept In-Reply-To: References: Message-ID: <2f741a063622ad482eb94ced3f16a216265eafd3.camel@joachim-breitner.de> Hi, merged! Joachim Am Dienstag, den 11.09.2018, 19:14 -0700 schrieb Vitaly Bragilevsky: > Hi all, > > The proposal "Lazy unboxed tuples / warn on unbanged strict patterns (#35)" (https://github.com/ghc-proposals/ghc-proposals/pull/35) is officially accepted since no complains received. > > Joachim, could you please label it as accepted on GitHub and do whatever should be done there? > > Regards, > Vitaly > > On Fri, Aug 24, 2018 at 5:11 PM Vitaly Bragilevsky wrote: > > Hi, > > > > This is my revised recommendation for the lazy unboxed tuples proposal (https://github.com/ghc-proposals/ghc-proposals/pull/35). It is already implemented, and I don't see strong opposition to it, so my recommendation is ACCEPT. > > > > Silence is understood as agreement. > > > > Regards, > > Vitaly > > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From rae at cs.brynmawr.edu Sat Sep 22 19:42:22 2018 From: rae at cs.brynmawr.edu (Richard Eisenberg) Date: Sat, 22 Sep 2018 15:42:22 -0400 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? Message-ID: Hi all, I imagine many of us are currently en route to St. Louis for this year's week of λ. I thought it might be nice for us steering committee members to gather, perhaps over lunch. My goal in organizing this is twofold: - Simply to gather. I enjoy working with you all and it's great to continue building social connections. - To figure out some concrete direction about the Linear Types proposal. As its shepherd, I feel responsible for moving it along and -- while there remains a slow drip of questions/answers/opinions on the ticket -- I don't sense that we're getting toward any concrete action that we can share with the authors of the proposal. I recognize that not all members of the committee will be at ICFP. Accordingly, I hope we can find a volunteer to take minutes to share with those not present. No concrete action will be committed to without posting here for discussion first. In addition, I'm sure we can find a way for folks to join the meeting remotely, if the timing works. I arbitrarily propose Monday lunch for this meeting. Feel free to counterpropose. See you soon, Richard From iavor.diatchki at gmail.com Sat Sep 22 20:04:56 2018 From: iavor.diatchki at gmail.com (Iavor Diatchki) Date: Sat, 22 Sep 2018 15:04:56 -0500 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: Message-ID: Hi, I think that's a good idea. Monday lunch works for me. Iavor PS: I just made it to St Louis, if anyone is interested in grabbing a beer and some food later today, drop me a message. On Sat, Sep 22, 2018, 2:47 PM Richard Eisenberg wrote: > Hi all, > > I imagine many of us are currently en route to St. Louis for this year's > week of λ. I thought it might be nice for us steering committee members to > gather, perhaps over lunch. My goal in organizing this is twofold: > > - Simply to gather. I enjoy working with you all and it's great to > continue building social connections. > - To figure out some concrete direction about the Linear Types proposal. > As its shepherd, I feel responsible for moving it along and -- while there > remains a slow drip of questions/answers/opinions on the ticket -- I don't > sense that we're getting toward any concrete action that we can share with > the authors of the proposal. > > I recognize that not all members of the committee will be at ICFP. > Accordingly, I hope we can find a volunteer to take minutes to share with > those not present. No concrete action will be committed to without posting > here for discussion first. In addition, I'm sure we can find a way for > folks to join the meeting remotely, if the timing works. > > I arbitrarily propose Monday lunch for this meeting. Feel free to > counterpropose. > > See you soon, > Richard > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marlowsd at gmail.com Sat Sep 22 22:37:59 2018 From: marlowsd at gmail.com (Simon Marlow) Date: Sat, 22 Sep 2018 23:37:59 +0100 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: Message-ID: Sounds good! Monday lunch also works for me. On Sat, 22 Sep 2018 at 20:47, Richard Eisenberg wrote: > Hi all, > > I imagine many of us are currently en route to St. Louis for this year's > week of λ. I thought it might be nice for us steering committee members to > gather, perhaps over lunch. My goal in organizing this is twofold: > > - Simply to gather. I enjoy working with you all and it's great to > continue building social connections. > - To figure out some concrete direction about the Linear Types proposal. > As its shepherd, I feel responsible for moving it along and -- while there > remains a slow drip of questions/answers/opinions on the ticket -- I don't > sense that we're getting toward any concrete action that we can share with > the authors of the proposal. > > I recognize that not all members of the committee will be at ICFP. > Accordingly, I hope we can find a volunteer to take minutes to share with > those not present. No concrete action will be committed to without posting > here for discussion first. In addition, I'm sure we can find a way for > folks to join the meeting remotely, if the timing works. > > I arbitrarily propose Monday lunch for this meeting. Feel free to > counterpropose. > > See you soon, > Richard > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric at seidel.io Sat Sep 22 22:40:51 2018 From: eric at seidel.io (Eric Seidel) Date: Sat, 22 Sep 2018 18:40:51 -0400 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: Message-ID: <1537656051.1565817.1517288296.2311709E@webmail.messagingengine.com> Monday works for me too! On Sat, Sep 22, 2018, at 18:37, Simon Marlow wrote: > Sounds good! Monday lunch also works for me. > > On Sat, 22 Sep 2018 at 20:47, Richard Eisenberg wrote: > > > Hi all, > > > > I imagine many of us are currently en route to St. Louis for this year's > > week of λ. I thought it might be nice for us steering committee members to > > gather, perhaps over lunch. My goal in organizing this is twofold: > > > > - Simply to gather. I enjoy working with you all and it's great to > > continue building social connections. > > - To figure out some concrete direction about the Linear Types proposal. > > As its shepherd, I feel responsible for moving it along and -- while there > > remains a slow drip of questions/answers/opinions on the ticket -- I don't > > sense that we're getting toward any concrete action that we can share with > > the authors of the proposal. > > > > I recognize that not all members of the committee will be at ICFP. > > Accordingly, I hope we can find a volunteer to take minutes to share with > > those not present. No concrete action will be committed to without posting > > here for discussion first. In addition, I'm sure we can find a way for > > folks to join the meeting remotely, if the timing works. > > > > I arbitrarily propose Monday lunch for this meeting. Feel free to > > counterpropose. > > > > See you soon, > > Richard > > _______________________________________________ > > ghc-steering-committee mailing list > > ghc-steering-committee at haskell.org > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee From ben at well-typed.com Sun Sep 23 01:52:39 2018 From: ben at well-typed.com (Ben Gamari) Date: Sat, 22 Sep 2018 21:52:39 -0400 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: Message-ID: <306A5D23-6B85-4B28-84D2-64BC6141BB89@well-typed.com> Monday sounds lovely On September 22, 2018 3:42:22 PM EDT, Richard Eisenberg wrote: >Hi all, > >I imagine many of us are currently en route to St. Louis for this >year's week of λ. I thought it might be nice for us steering committee >members to gather, perhaps over lunch. My goal in organizing this is >twofold: > >- Simply to gather. I enjoy working with you all and it's great to >continue building social connections. >- To figure out some concrete direction about the Linear Types >proposal. As its shepherd, I feel responsible for moving it along and >-- while there remains a slow drip of questions/answers/opinions on the >ticket -- I don't sense that we're getting toward any concrete action >that we can share with the authors of the proposal. > >I recognize that not all members of the committee will be at ICFP. >Accordingly, I hope we can find a volunteer to take minutes to share >with those not present. No concrete action will be committed to without >posting here for discussion first. In addition, I'm sure we can find a >way for folks to join the meeting remotely, if the timing works. > >I arbitrarily propose Monday lunch for this meeting. Feel free to >counterpropose. > >See you soon, >Richard >_______________________________________________ >ghc-steering-committee mailing list >ghc-steering-committee at haskell.org >https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From simonpj at microsoft.com Sun Sep 23 01:59:36 2018 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Sun, 23 Sep 2018 01:59:36 +0000 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: Message-ID: Good idea. It sounds as if everyone else can make Monday lunch, but sadly I can't. Nor Tues. Do go ahead without me - I may try to rearrange my commitment S | -----Original Message----- | From: ghc-steering-committee On Behalf Of Richard Eisenberg | Sent: 22 September 2018 20:42 | To: ghc-steering-committee | Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? | | Hi all, | | I imagine many of us are currently en route to St. Louis for this year's | week of λ. I thought it might be nice for us steering committee members | to gather, perhaps over lunch. My goal in organizing this is twofold: | | - Simply to gather. I enjoy working with you all and it's great to | continue building social connections. | - To figure out some concrete direction about the Linear Types proposal. | As its shepherd, I feel responsible for moving it along and -- while | there remains a slow drip of questions/answers/opinions on the ticket -- | I don't sense that we're getting toward any concrete action that we can | share with the authors of the proposal. | | I recognize that not all members of the committee will be at ICFP. | Accordingly, I hope we can find a volunteer to take minutes to share | with those not present. No concrete action will be committed to without | posting here for discussion first. In addition, I'm sure we can find a | way for folks to join the meeting remotely, if the timing works. | | I arbitrarily propose Monday lunch for this meeting. Feel free to | counterpropose. | | See you soon, | Richard | _______________________________________________ | ghc-steering-committee mailing list | ghc-steering-committee at haskell.org | https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee From chak at justtesting.org Sun Sep 23 11:40:23 2018 From: chak at justtesting.org (Manuel M T Chakravarty) Date: Sun, 23 Sep 2018 13:40:23 +0200 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: Message-ID: I won’t be at ICFP. Have fun, Manuel > Am 22.09.2018 um 21:42 schrieb Richard Eisenberg : > > Hi all, > > I imagine many of us are currently en route to St. Louis for this year's week of λ. I thought it might be nice for us steering committee members to gather, perhaps over lunch. My goal in organizing this is twofold: > > - Simply to gather. I enjoy working with you all and it's great to continue building social connections. > - To figure out some concrete direction about the Linear Types proposal. As its shepherd, I feel responsible for moving it along and -- while there remains a slow drip of questions/answers/opinions on the ticket -- I don't sense that we're getting toward any concrete action that we can share with the authors of the proposal. > > I recognize that not all members of the committee will be at ICFP. Accordingly, I hope we can find a volunteer to take minutes to share with those not present. No concrete action will be committed to without posting here for discussion first. In addition, I'm sure we can find a way for folks to join the meeting remotely, if the timing works. > > I arbitrarily propose Monday lunch for this meeting. Feel free to counterpropose. > > See you soon, > Richard > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee From simonpj at microsoft.com Sun Sep 23 16:23:01 2018 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Sun, 23 Sep 2018 16:23:01 +0000 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: Message-ID: I rearranged. Monday lunch is now fine for me. Simon | -----Original Message----- | From: ghc-steering-committee On Behalf Of Simon Peyton Jones via ghc-steering- | committee | Sent: 23 September 2018 03:00 | To: Richard Eisenberg ; ghc-steering-committee | | Subject: Re: [ghc-steering-committee] GHC steering committee lunch at | ICFP? | | Good idea. It sounds as if everyone else can make Monday lunch, but | sadly I can't. Nor Tues. Do go ahead without me - I may try to | rearrange my commitment | | S | | | -----Original Message----- | | From: ghc-steering-committee On Behalf Of Richard Eisenberg | | Sent: 22 September 2018 20:42 | | To: ghc-steering-committee | | Subject: [ghc-steering-committee] GHC steering committee lunch at | ICFP? | | | | Hi all, | | | | I imagine many of us are currently en route to St. Louis for this | year's | | week of λ. I thought it might be nice for us steering committee | members | | to gather, perhaps over lunch. My goal in organizing this is twofold: | | | | - Simply to gather. I enjoy working with you all and it's great to | | continue building social connections. | | - To figure out some concrete direction about the Linear Types | proposal. | | As its shepherd, I feel responsible for moving it along and -- while | | there remains a slow drip of questions/answers/opinions on the ticket | -- | | I don't sense that we're getting toward any concrete action that we | can | | share with the authors of the proposal. | | | | I recognize that not all members of the committee will be at ICFP. | | Accordingly, I hope we can find a volunteer to take minutes to share | | with those not present. No concrete action will be committed to | without | | posting here for discussion first. In addition, I'm sure we can find a | | way for folks to join the meeting remotely, if the timing works. | | | | I arbitrarily propose Monday lunch for this meeting. Feel free to | | counterpropose. | | | | See you soon, | | Richard | | _______________________________________________ | | ghc-steering-committee mailing list | | ghc-steering-committee at haskell.org | | https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering- | committee | _______________________________________________ | ghc-steering-committee mailing list | ghc-steering-committee at haskell.org | https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee From rae at cs.brynmawr.edu Sun Sep 23 16:44:16 2018 From: rae at cs.brynmawr.edu (Richard Eisenberg) Date: Sun, 23 Sep 2018 11:44:16 -0500 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: Message-ID: <0BB25AD0-3EB5-47D6-A579-70A315833595@cs.brynmawr.edu> OK -- I will try to reserve a table in a corner of the lunch area. (More information tomorrow once I can actually see the lunch area.) Note that we have only an hour until the first session after lunch. Any updates (e.g., specific location if it's hard to find) will appear here. If you are not at ICFP but would like to join remotely, email me and we'll figure out a way. This meeting will take place at 1700-1800 GMT on Monday. See many of you tomorrow, Richard > On Sep 23, 2018, at 11:23 AM, Simon Peyton Jones wrote: > > I rearranged. Monday lunch is now fine for me. > > Simon > > | -----Original Message----- > | From: ghc-steering-committee | bounces at haskell.org> On Behalf Of Simon Peyton Jones via ghc-steering- > | committee > | Sent: 23 September 2018 03:00 > | To: Richard Eisenberg ; ghc-steering-committee > | > | Subject: Re: [ghc-steering-committee] GHC steering committee lunch at > | ICFP? > | > | Good idea. It sounds as if everyone else can make Monday lunch, but > | sadly I can't. Nor Tues. Do go ahead without me - I may try to > | rearrange my commitment > | > | S > | > | | -----Original Message----- > | | From: ghc-steering-committee | | bounces at haskell.org> On Behalf Of Richard Eisenberg > | | Sent: 22 September 2018 20:42 > | | To: ghc-steering-committee > | | Subject: [ghc-steering-committee] GHC steering committee lunch at > | ICFP? > | | > | | Hi all, > | | > | | I imagine many of us are currently en route to St. Louis for this > | year's > | | week of λ. I thought it might be nice for us steering committee > | members > | | to gather, perhaps over lunch. My goal in organizing this is twofold: > | | > | | - Simply to gather. I enjoy working with you all and it's great to > | | continue building social connections. > | | - To figure out some concrete direction about the Linear Types > | proposal. > | | As its shepherd, I feel responsible for moving it along and -- while > | | there remains a slow drip of questions/answers/opinions on the ticket > | -- > | | I don't sense that we're getting toward any concrete action that we > | can > | | share with the authors of the proposal. > | | > | | I recognize that not all members of the committee will be at ICFP. > | | Accordingly, I hope we can find a volunteer to take minutes to share > | | with those not present. No concrete action will be committed to > | without > | | posting here for discussion first. In addition, I'm sure we can find a > | | way for folks to join the meeting remotely, if the timing works. > | | > | | I arbitrarily propose Monday lunch for this meeting. Feel free to > | | counterpropose. > | | > | | See you soon, > | | Richard > | | _______________________________________________ > | | ghc-steering-committee mailing list > | | ghc-steering-committee at haskell.org > | | https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering- > | committee > | _______________________________________________ > | ghc-steering-committee mailing list > | ghc-steering-committee at haskell.org > | https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee From mail at joachim-breitner.de Sun Sep 23 19:03:37 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Sun, 23 Sep 2018 14:03:37 -0500 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: <0BB25AD0-3EB5-47D6-A579-70A315833595@cs.brynmawr.edu> References: <0BB25AD0-3EB5-47D6-A579-70A315833595@cs.brynmawr.edu> Message-ID: Hi, Monday lunch works for me. Cheers, Joachim Am Sonntag, den 23.09.2018, 11:44 -0500 schrieb Richard Eisenberg: > OK -- I will try to reserve a table in a corner of the lunch area. (More information tomorrow once I can actually see the lunch area.) > > Note that we have only an hour until the first session after lunch. > > Any updates (e.g., specific location if it's hard to find) will appear here. > > If you are not at ICFP but would like to join remotely, email me and we'll figure out a way. This meeting will take place at 1700-1800 GMT on Monday. > > See many of you tomorrow, > Richard > > > On Sep 23, 2018, at 11:23 AM, Simon Peyton Jones wrote: > > > > I rearranged. Monday lunch is now fine for me. > > > > Simon > > > > > -----Original Message----- > > > From: ghc-steering-committee > > bounces at haskell.org> On Behalf Of Simon Peyton Jones via ghc-steering- > > > committee > > > Sent: 23 September 2018 03:00 > > > To: Richard Eisenberg ; ghc-steering-committee > > > > > > Subject: Re: [ghc-steering-committee] GHC steering committee lunch at > > > ICFP? > > > > > > Good idea. It sounds as if everyone else can make Monday lunch, but > > > sadly I can't. Nor Tues. Do go ahead without me - I may try to > > > rearrange my commitment > > > > > > S > > > > > > > -----Original Message----- > > > > From: ghc-steering-committee > > > bounces at haskell.org> On Behalf Of Richard Eisenberg > > > > Sent: 22 September 2018 20:42 > > > > To: ghc-steering-committee > > > > Subject: [ghc-steering-committee] GHC steering committee lunch at > > > > > > ICFP? > > > > > > > > Hi all, > > > > > > > > I imagine many of us are currently en route to St. Louis for this > > > > > > year's > > > > week of λ. I thought it might be nice for us steering committee > > > > > > members > > > > to gather, perhaps over lunch. My goal in organizing this is twofold: > > > > > > > > - Simply to gather. I enjoy working with you all and it's great to > > > > continue building social connections. > > > > - To figure out some concrete direction about the Linear Types > > > > > > proposal. > > > > As its shepherd, I feel responsible for moving it along and -- while > > > > there remains a slow drip of questions/answers/opinions on the ticket > > > > > > -- > > > > I don't sense that we're getting toward any concrete action that we > > > > > > can > > > > share with the authors of the proposal. > > > > > > > > I recognize that not all members of the committee will be at ICFP. > > > > Accordingly, I hope we can find a volunteer to take minutes to share > > > > with those not present. No concrete action will be committed to > > > > > > without > > > > posting here for discussion first. In addition, I'm sure we can find a > > > > way for folks to join the meeting remotely, if the timing works. > > > > > > > > I arbitrarily propose Monday lunch for this meeting. Feel free to > > > > counterpropose. > > > > > > > > See you soon, > > > > Richard > > > > _______________________________________________ > > > > ghc-steering-committee mailing list > > > > ghc-steering-committee at haskell.org > > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering- > > > > > > committee > > > _______________________________________________ > > > ghc-steering-committee mailing list > > > ghc-steering-committee at haskell.org > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From rae at cs.brynmawr.edu Mon Sep 24 15:58:39 2018 From: rae at cs.brynmawr.edu (Richard Eisenberg) Date: Mon, 24 Sep 2018 10:58:39 -0500 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: <0BB25AD0-3EB5-47D6-A579-70A315833595@cs.brynmawr.edu> References: <0BB25AD0-3EB5-47D6-A579-70A315833595@cs.brynmawr.edu> Message-ID: <45084B59-9C3F-4B38-95AD-66ADB0A6D06E@cs.brynmawr.edu> I've learned there is no proper lunch room. However, on the east side of the building is some space we may be able to use. (This is to the right as you exit the auditorium or to the left as you enter the building.) Let's find each other there (down a small flight of stairs). Thanks, Richard > On Sep 23, 2018, at 11:44 AM, Richard Eisenberg wrote: > > OK -- I will try to reserve a table in a corner of the lunch area. (More information tomorrow once I can actually see the lunch area.) > > Note that we have only an hour until the first session after lunch. > > Any updates (e.g., specific location if it's hard to find) will appear here. > > If you are not at ICFP but would like to join remotely, email me and we'll figure out a way. This meeting will take place at 1700-1800 GMT on Monday. > > See many of you tomorrow, > Richard > >> On Sep 23, 2018, at 11:23 AM, Simon Peyton Jones wrote: >> >> I rearranged. Monday lunch is now fine for me. >> >> Simon >> >> | -----Original Message----- >> | From: ghc-steering-committee > | bounces at haskell.org> On Behalf Of Simon Peyton Jones via ghc-steering- >> | committee >> | Sent: 23 September 2018 03:00 >> | To: Richard Eisenberg ; ghc-steering-committee >> | >> | Subject: Re: [ghc-steering-committee] GHC steering committee lunch at >> | ICFP? >> | >> | Good idea. It sounds as if everyone else can make Monday lunch, but >> | sadly I can't. Nor Tues. Do go ahead without me - I may try to >> | rearrange my commitment >> | >> | S >> | >> | | -----Original Message----- >> | | From: ghc-steering-committee > | | bounces at haskell.org> On Behalf Of Richard Eisenberg >> | | Sent: 22 September 2018 20:42 >> | | To: ghc-steering-committee >> | | Subject: [ghc-steering-committee] GHC steering committee lunch at >> | ICFP? >> | | >> | | Hi all, >> | | >> | | I imagine many of us are currently en route to St. Louis for this >> | year's >> | | week of λ. I thought it might be nice for us steering committee >> | members >> | | to gather, perhaps over lunch. My goal in organizing this is twofold: >> | | >> | | - Simply to gather. I enjoy working with you all and it's great to >> | | continue building social connections. >> | | - To figure out some concrete direction about the Linear Types >> | proposal. >> | | As its shepherd, I feel responsible for moving it along and -- while >> | | there remains a slow drip of questions/answers/opinions on the ticket >> | -- >> | | I don't sense that we're getting toward any concrete action that we >> | can >> | | share with the authors of the proposal. >> | | >> | | I recognize that not all members of the committee will be at ICFP. >> | | Accordingly, I hope we can find a volunteer to take minutes to share >> | | with those not present. No concrete action will be committed to >> | without >> | | posting here for discussion first. In addition, I'm sure we can find a >> | | way for folks to join the meeting remotely, if the timing works. >> | | >> | | I arbitrarily propose Monday lunch for this meeting. Feel free to >> | | counterpropose. >> | | >> | | See you soon, >> | | Richard >> | | _______________________________________________ >> | | ghc-steering-committee mailing list >> | | ghc-steering-committee at haskell.org >> | | https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering- >> | committee >> | _______________________________________________ >> | ghc-steering-committee mailing list >> | ghc-steering-committee at haskell.org >> | https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee From ben at well-typed.com Mon Sep 24 16:13:56 2018 From: ben at well-typed.com (Ben Gamari) Date: Mon, 24 Sep 2018 12:13:56 -0400 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: <45084B59-9C3F-4B38-95AD-66ADB0A6D06E@cs.brynmawr.edu> References: <0BB25AD0-3EB5-47D6-A579-70A315833595@cs.brynmawr.edu> <45084B59-9C3F-4B38-95AD-66ADB0A6D06E@cs.brynmawr.edu> Message-ID: <878t3q27r1.fsf@smart-cactus.org> Richard Eisenberg writes: > I've learned there is no proper lunch room. However, on the east side > of the building is some space we may be able to use. (This is to the > right as you exit the auditorium or to the left as you enter the > building.) Let's find each other there (down a small flight of > stairs). > I realized that I am not registered for today so I may need to run out to pick up some lunch from outside the venue then find you all. Cheers, - Ben -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 487 bytes Desc: not available URL: From marlowsd at gmail.com Mon Sep 24 17:10:12 2018 From: marlowsd at gmail.com (Simon Marlow) Date: Mon, 24 Sep 2018 12:10:12 -0500 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: <878t3q27r1.fsf@smart-cactus.org> References: <0BB25AD0-3EB5-47D6-A579-70A315833595@cs.brynmawr.edu> <45084B59-9C3F-4B38-95AD-66ADB0A6D06E@cs.brynmawr.edu> <878t3q27r1.fsf@smart-cactus.org> Message-ID: I will be a little late too, left my badge with my lunch ticket at the hotel :( On Mon, 24 Sep 2018, 11:14 Ben Gamari, wrote: > Richard Eisenberg writes: > > > I've learned there is no proper lunch room. However, on the east side > > of the building is some space we may be able to use. (This is to the > > right as you exit the auditorium or to the left as you enter the > > building.) Let's find each other there (down a small flight of > > stairs). > > > I realized that I am not registered for today so I may need to run out > to pick up some lunch from outside the venue then find you all. > > Cheers, > > - Ben > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > -------------- next part -------------- An HTML attachment was scrubbed... URL: From iavor.diatchki at gmail.com Mon Sep 24 17:19:24 2018 From: iavor.diatchki at gmail.com (Iavor Diatchki) Date: Mon, 24 Sep 2018 12:19:24 -0500 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: <0BB25AD0-3EB5-47D6-A579-70A315833595@cs.brynmawr.edu> <45084B59-9C3F-4B38-95AD-66ADB0A6D06E@cs.brynmawr.edu> <878t3q27r1.fsf@smart-cactus.org> Message-ID: There's a space with a few chairs on the first floor next to the restroom. Is this what you meant? I am in there anyway :) On Sep 24, 2018 12:10 PM, "Simon Marlow" wrote: I will be a little late too, left my badge with my lunch ticket at the hotel :( On Mon, 24 Sep 2018, 11:14 Ben Gamari, wrote: > Richard Eisenberg writes: > > > I've learned there is no proper lunch room. However, on the east side > > of the building is some space we may be able to use. (This is to the > > right as you exit the auditorium or to the left as you enter the > > building.) Let's find each other there (down a small flight of > > stairs). > > > I realized that I am not registered for today so I may need to run out > to pick up some lunch from outside the venue then find you all. > > Cheers, > > - Ben > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee at haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at joachim-breitner.de Mon Sep 24 17:46:41 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Mon, 24 Sep 2018 12:46:41 -0500 Subject: [ghc-steering-committee] GHC steering committee lunch at ICFP? In-Reply-To: References: <0BB25AD0-3EB5-47D6-A579-70A315833595@cs.brynmawr.edu> <45084B59-9C3F-4B38-95AD-66ADB0A6D06E@cs.brynmawr.edu> <878t3q27r1.fsf@smart-cactus.org> Message-ID: <28027409-086A-4C8F-B6B6-F4391152C5D4@joachim-breitner.de> Hi, Sorry, didn't see your message. You are definitely not where we are :-/ Joachim Am 24. September 2018 12:19:24 GMT-05:00 schrieb Iavor Diatchki : >There's a space with a few chairs on the first floor next to the >restroom. >Is this what you meant? I am in there anyway :) > >On Sep 24, 2018 12:10 PM, "Simon Marlow" wrote: > >I will be a little late too, left my badge with my lunch ticket at the >hotel :( > >On Mon, 24 Sep 2018, 11:14 Ben Gamari, wrote: > >> Richard Eisenberg writes: >> >> > I've learned there is no proper lunch room. However, on the east >side >> > of the building is some space we may be able to use. (This is to >the >> > right as you exit the auditorium or to the left as you enter the >> > building.) Let's find each other there (down a small flight of >> > stairs). >> > >> I realized that I am not registered for today so I may need to run >out >> to pick up some lunch from outside the venue then find you all. >> >> Cheers, >> >> - Ben >> _______________________________________________ >> ghc-steering-committee mailing list >> ghc-steering-committee at haskell.org >> >https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee >> >_______________________________________________ >ghc-steering-committee mailing list >ghc-steering-committee at haskell.org >https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee From mail at joachim-breitner.de Sun Sep 30 17:33:50 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Sun, 30 Sep 2018 10:33:50 -0700 Subject: [ghc-steering-committee] StableName guarantee (#163), recommendation: accept In-Reply-To: <2441e076867c5e8ed40f4f0e572c2b718cccff42.camel@joachim-breitner.de> References: <2441e076867c5e8ed40f4f0e572c2b718cccff42.camel@joachim-breitner.de> Message-ID: <698e6216b0bb63d09e2a951d916e7bf98b597b98.camel@joachim-breitner.de> Hi, (listening to the sound of silence for a while) accepted! Joachim Am Montag, den 10.09.2018, 09:45 +0200 schrieb Joachim Breitner: > SGTM > > (sounds good to me) > > I like the easy ones :-) > > Am Montag, den 10.09.2018, 08:13 +0100 schrieb Simon Marlow: > > The proposer wants to change the implementation of StableNames, and noticed that the existing implementation has the property that, for two StableNames s1 and s2 that are currently live, > > > > hashStableName s1 == hashStableName s2 ==> s1 == s2 > > > > this property is not documented. As far as we know, there isn't any code in the wild that relies on it. In fact, relying on it would be tricky due to the requirement that s1 and s2 have to be live - as soon as a StableName becomes unreachable from the GC's point of view, the index into the table that is used to provide the result of hashStableName is reused. > > > > The proposal is to remove this property. Well, a future refactoring of the StableName implemnetation would actually remove the property, the proposer wants the committee to consider whether the property in question is worth keeping (and therefore documenting). > > > > I think it's pretty clear that we don't want to document this property, because in order to do so we would have to give a precise definition of what "live" means, which is not possible. Furthermore, we don't know of any use cases in the wild. So, let's accept the proposal. > > > > Cheers > > Simon > > _______________________________________________ > > ghc-steering-committee mailing list > > ghc-steering-committee at haskell.org > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From mail at joachim-breitner.de Sun Sep 30 17:38:58 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Sun, 30 Sep 2018 10:38:58 -0700 Subject: [ghc-steering-committee] Proposal #168: fail with OverloadedStrings, rec: accept Message-ID: Dear committee, welcome back from ICFP! Those who missed it: it was great, watch the videos, come to Berlin next year. Shayne Fletcher proposed that in the presence of both RebindableSyntax and OverloadedStrings, the implicit calls to fail produces by the compiler should wrap the arguments in `fromString`: https://github.com/shayne-fletcher-da/ghc-proposals/blob/fail-rebindable-with-overloaded-strings/proposals/0000-fail-rebindable-with-overloaded-strings.rst I’ll shepherd that myself. I agree with Neil Mitchell in the assessment that this feels more like a bug fix than a proposal, and support acceptance. Cheers, Joachim -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From mail at joachim-breitner.de Sun Sep 30 17:42:27 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Sun, 30 Sep 2018 10:42:27 -0700 Subject: [ghc-steering-committee] Please Review #170: Uppercase OverloadedLabels, Shepherd: Vitaly Bragilevsky Message-ID: Dear Committee, this is your secretary speaking: Uppercase OverloadedLabels, by howtonotwin Maguirer, was proposed https://github.com/ghc-proposals/ghc-proposals/pull/170 I propose Vitaly Bragilevsky as the shepherd. Please reach consensus as described in https://github.com/ghc-proposals/ghc-proposals#committee-process I suggest you make a recommendation, in a new e-mail thread with the proposal number in the subject, about the decision, maybe point out debatable points, and assume that anyone who stays quiet agrees with you. Thanks, Joachim -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From mail at joachim-breitner.de Sun Sep 30 17:46:58 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Sun, 30 Sep 2018 10:46:58 -0700 Subject: [ghc-steering-committee] Proposal: Syntax for visible dependent quantification (#81) In-Reply-To: References: <30B357D6-E03C-4A03-8D6C-F5BF22BF0E13@cs.brynmawr.edu> <88AAAB4F-4C45-43EF-B4A4-D095982FCBDF@cs.brynmawr.edu> <4704D092-353A-4113-9B2F-482FD3F7D1AF@cs.brynmawr.edu> <52a0e1ee2494f5514ddda0984b31844dcf7b76a2.camel@joachim-breitner.de> Message-ID: <9e39244f1ccb8c760df3aa334a3b32df1ee867a3.camel@joachim-breitner.de> Hi, guess we have consensus. Accepted. Joachim Am Freitag, den 17.08.2018, 11:19 +0000 schrieb Simon Peyton Jones via ghc-steering-committee: > I support this #81. > > Simon > > From: ghc-steering-committee On Behalf Of Roman Leshchinskiy > Sent: 09 August 2018 19:44 > To: Joachim Breitner > Cc: ghc-steering-committee at haskell.org > Subject: Re: [ghc-steering-committee] Proposal: Syntax for visible dependent quantification (#81) > > Sorry for the long delay. Given that the general feedback is positive and #102 is now available, I recommend that we accept #81. > > Thanks, > > Roman > > On Sat, May 5, 2018 at 10:12 PM, Joachim Breitner wrote: > > Hi, > > > > indeed, we should make progress here. Roman, with #102 discussed > > (albeit not decided), what is your recommendation about #81? > > > > Cheers, > > Joachim > > > > Am Sonntag, den 15.04.2018, 23:09 -0400 schrieb Richard Eisenberg: > > > Hi committee, > > > > > > I'd like to reboot this discussion, now that #102 has been written, debated, and tabled. As a reminder, this proposal is blocking #54, which will cure real bugs GHC is plagued by. > > > > > > Thanks! > > > Richard > > > > > > > On Jan 5, 2018, at 8:37 PM, Richard Eisenberg wrote: > > > > > > > > OK. I've posted proposal #102 (https://github.com/goldfirere/ghc-proposals/blob/pi/proposals/0000-pi.rst) which describes the full set of quantifiers for Dependent Haskell. > > > > > > > > I continue to think that #81 can stand alone, but those who want a larger picture can see #102 for that larger picture. > > > > > > > > Thanks, > > > > Richard > > > > > > > > > On Dec 21, 2017, at 9:15 AM, Richard Eisenberg wrote: > > > > > > > > > > These are good suggestions. Thanks. While I'm writing all these proposals, it's about time I introduce pi proper -- the proposal for pi can go further than reserve syntax, because there are already places in the language that support real pi-types (the kinds of type families [assuming #54 is accepted] and the kinds of datatypes). > > > > > > > > > > I'll put together yet another proposal. :) > > > > > > > > > > Regardless, I don't want to shut down debate on this proposal in isolation. In particular, I'd love new syntax suggestions, as I agree that the proposed syntax is a little subtle. > > > > > > > > > > Thanks, > > > > > Richard > > > > > > > > > > > On Dec 20, 2017, at 3:35 PM, Roman Leshchinskiy wrote: > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > The proposal is about adding support for dependent quantification to > > > > > > kind signatures: > > > > > > > > > > > > https://github.com/ghc-proposals/ghc-proposals/pull/81 > > > > > > > > > > > > Consider the following declaration (example lifted from the proposal): > > > > > > > > > > > > data T k (a :: k) > > > > > > > > > > > > GHC accepts this but it can't be given an explicit kind. Internally, > > > > > > it is assigned a kind which is rendered as > > > > > > > > > > > > forall k -> k -> * > > > > > > > > > > > > but this isn't accepted in source code. Note that in applications of > > > > > > T, k must be specified explicitly (e.g., T Type Int) which is why T > > > > > > does *not* have the kind > > > > > > > > > > > > forall k. k -> * > > > > > > > > > > > > Moreover, k is mentioned later in the kind which is why something like > > > > > > Type -> k -> * doesn't work, either. > > > > > > > > > > > > The proposal is to allow forall k -> k -> * and similar kinds to > > > > > > appear in source code. > > > > > > > > > > > > This is actually intended as the first in a series of proposals > > > > > > driving us towards dependent types in Haskell as described in > > > > > > Richard's thesis > > > > > > (https://www.cis.upenn.edu/~sweirich/papers/eisenberg-thesis.pdf). > > > > > > Ultimately, the intention is to have all of the following (cf. Chapter > > > > > > 4 of the thesis): > > > > > > > > > > > > forall a. t > > > > > > forall a -> t > > > > > > pi a. t > > > > > > pi a -> t > > > > > > > > > > > > Here, forall and pi express relevance (does it exist at runtime) and . > > > > > > and -> express visibility (does it have to be specified explicitly). > > > > > > > > > > > > Because of this, my recommendation is to strongly encourage the author > > > > > > to submit an extended proposal which reserves (but doesn't specify the > > > > > > semantics of) the above syntax wholesale. > > > > > > > > > > > > This would allow us to ensure that various bits of Dependent Haskell > > > > > > use consistent syntax and language extensions once implemented. I find > > > > > > it quite difficult to discuss just this specific bit of syntax in > > > > > > isolation. Indeed, the public discussion was rather confused without > > > > > > an explanation of the roadmap > > > > > > (https://github.com/ghc-proposals/ghc-proposals/pull/81#issuecomment-336892922). > > > > > > > > > > > > Alternatively, we could just agree on the roadmap ourselves, without > > > > > > public discussion. This would somewhat circumvent the process, though. > > > > > > > > > > > > If we decide to discuss just the proposal as is, though, then I'd be > > > > > > weakly against the proposed syntax as it is too subtle for my taste > > > > > > and abuses familiar mathematical notation somewhat. I'd probably > > > > > > prefer something like: > > > > > > > > > > > > type a -> t > > > > > > > > > > > > The proposal also doesn't specify what language extension would turn > > > > > > on support for the syntax so this would have to be rectified. > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Roman > > > > > > _______________________________________________ > > > > > > ghc-steering-committee mailing list > > > > > > ghc-steering-committee at haskell.org > > > > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > > > > > > > > _______________________________________________ > > > > > ghc-steering-committee mailing list > > > > > ghc-steering-committee at haskell.org > > > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > > > > _______________________________________________ > > > ghc-steering-committee mailing list > > > ghc-steering-committee at haskell.org > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > _______________________________________________ > > ghc-steering-committee mailing list > > ghc-steering-committee at haskell.org > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From mail at joachim-breitner.de Sun Sep 30 17:50:05 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Sun, 30 Sep 2018 10:50:05 -0700 Subject: [ghc-steering-committee] Proposal: Top-level kind signatures (#54) In-Reply-To: References: Message-ID: <59fc59959fb70f4059e1e0e06e8c72794e196089.camel@joachim-breitner.de> Hi, Am Freitag, den 17.08.2018, 11:24 +0000 schrieb Simon Peyton Jones via ghc-steering-committee: > I’m strongly in favour of #54. and nobody disagrees, accepted. Cheers, Joachim -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From mail at joachim-breitner.de Sun Sep 30 17:53:44 2018 From: mail at joachim-breitner.de (Joachim Breitner) Date: Sun, 30 Sep 2018 10:53:44 -0700 Subject: [ghc-steering-committee] Status Message-ID: <0a00af411b53ad6aa09f33584c5205ca8dfdd693.camel@joachim-breitner.de> Hi committee, post ICFP status update. Since the last status update, we * were asked to review these proposals: #163 StableName guarantee (Shepherd: Simon M.) #164 Show Types as Symbols (Shepherd: Richard) #168 fail with OverloadedStrings (Shepherd: Joachim) #170 Uppercase OverloadedLabels (Shepherd: Vitaly) * got a recommendation from shepherds about: #81 Syntax for visible dependent quantification (rec: accept) #54 Top-level kind signatures (rec: accept) #106 Define Kinds Without Promotion (rec: accept) #35 Lazy unboxed tuples (rec: reject, I mean, accept) #163 StableName guarantee (rec: accept) #168: fail with OverloadedStrings (rec: accept) * decided about the following proposals #126 Type applications in patterns (accept) #35 Lazy unboxed tuples (accept) #106 Define Kinds Without Promotion (accept) #163 StableName guarantee (accept) #81 Syntax for visible dependent quantification (accept) #54 Top-level kind signatures (accept) With Roman’s proposals successfully concluded, I’d like to officially thank him for his contributions to the committee, and relieve him from his obligations as a committee member. We currently have to act on the following 9 proposals, which is 2 less than last round. Let’s make that a trend! Uppercase OverloadedLables https://github.com/ghc-proposals/ghc-proposals/pull/170 Shepherd: Vitaly Status: Waiting for recommendation. fail with OverloadedStrings https://github.com/ghc-proposals/ghc-proposals/pull/168 Shepherd: Joachim Status: Acceptance recommended Show Types as Symbols https://github.com/ghc-proposals/ghc-proposals/pull/164 Shepherd: Richard Status: Richard is discussing things with the authors Type annotated quoters https://github.com/ghc-proposals/ghc-proposals/pull/125 Shepherd: Manuel Status: Still waiting for recommendation. Manuel? Provenance-Qualified Package Imports https://github.com/ghc-proposals/ghc-proposals/pull/115 Shepherd: Ben Status: Still waiting for recommendation. This is pretty old! Linear types https://github.com/ghc-proposals/ghc-proposals/pull/111 Shepherd: Richard Status: acceptance-ish(?) … this is a hard one ExtraCommas https://github.com/ghc-proposals/ghc-proposals/pull/87 Shepherd: Chris Recommendation: accept Status: Met with some reservation. Chris, what is the status of discussion? Or-Patterns https://github.com/ghc-proposals/ghc-proposals/pull/43 Shepherd: Manuel Recommendation: accept Status: Round 2 discussion ebbed down. Manuel? Bundling patterns with synonyms https://github.com/ghc-proposals/ghc-proposals/pull/28 Shepherd: Chris Recommendation: accept Status: Ongoing discussion, met with some resistance. Chris, what’s the status? Cheers, Joachim -- Joachim Breitner mail at joachim-breitner.de http://www.joachim-breitner.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From bravit111 at gmail.com Sun Sep 30 19:16:53 2018 From: bravit111 at gmail.com (Vitaly Bragilevsky) Date: Sun, 30 Sep 2018 12:16:53 -0700 Subject: [ghc-steering-committee] Proposal #170: Uppercase OverloadedLabels, rec: accept Message-ID: Hi all, As a shepherd to the proposal #170, Uppercase OverloadedLabels ( https://github.com/ghc-proposals/ghc-proposals/pull/170) proposed by howtonotwin, I recommend acceptance. It is proposed to allow the string after # (with -XOverloadedLabels) to start uppercase thus looking like a constructor name in addition to a variable name as we have now. The proposal is clear, there are no known pitfalls. I suggest having two weeks for discussion. Silence is understood as an an agreement with this recommendation. Regards, Vitaly -------------- next part -------------- An HTML attachment was scrubbed... URL: From cma at bitemyapp.com Sun Sep 30 19:22:16 2018 From: cma at bitemyapp.com (Christopher Allen) Date: Sun, 30 Sep 2018 14:22:16 -0500 Subject: [ghc-steering-committee] Bundling patterns with type synonyms (#28) In-Reply-To: <08573db359ccbefa07080c28884667d56bde207d.camel@joachim-breitner.de> References: <61FD037C-4A8F-45F2-A0E1-9010380F8029@cs.brynmawr.edu> <08573db359ccbefa07080c28884667d56bde207d.camel@joachim-breitner.de> Message-ID: I think based on what transpired in this thread and on the GitHub PR, the proposal should be rejected. My reasoning: - There was a more general way to solve the problem outlined by Simon. - The complexity doesn't pay for itself, esp. given how particular the problem it solves is. What do y'all think? On Sat, Aug 4, 2018 at 10:35 AM Joachim Breitner wrote: > > Hi, > > we have disagreement here. Chris, would you steer us towards consensus? > > Cheers, > Joachim > > Am Samstag, den 23.06.2018, 23:19 -0400 schrieb Richard Eisenberg: > > Agreed. Beyond my posted technical reservations, I believe that a better solution is out there. > > > > Richard > > > > > On Jun 23, 2018, at 1:00 PM, Joachim Breitner wrote: > > > > > > Hi, > > > > > > Am Mittwoch, den 13.06.2018, 18:18 -0500 schrieb Christopher Allen: > > > > Bundling patterns with type synonyms by Bertram Felgenhauer and Joe Hermaszewski > > > > > > > > https://github.com/ghc-proposals/ghc-proposals/pull/28 > > > > > > > > > > > > I think we should accept this proposal. There are a couple of > > > > open questions, ambiguities, and potential downsides but the overall > > > > complexity of the proposal doesn't cause me great concern. > > > > > > I agree with Simon that might not take the language in the direction we > > > want to take it. > > > > > > In fact, if we had PatternSynonyms and ExplicitNamespaces back when > > > Haskell was first specified, we might not have the T(K) syntax at all, > > > and just a flat, explicit list of names, possibly requiring explicit > > > namespace qualifier to disambiguate? Things like deprecating exports > > > would have been easier then… > > > > > > So while I follow the motivation of the proposal, and I don’t have > > > concrete other solution to offer, I am inclined to reject it: The > > > problem it is solving does not seem to be too urgent, and my gut > > > feeling says that there might be something better down the road. > > > > > > Cheers, > > > Joachim > > > > > > -- > > > Joachim Breitner > > > mail at joachim-breitner.de > > > http://www.joachim-breitner.de/ > > > _______________________________________________ > > > ghc-steering-committee mailing list > > > ghc-steering-committee at haskell.org > > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > > > > _______________________________________________ > > ghc-steering-committee mailing list > > ghc-steering-committee at haskell.org > > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee > -- > Joachim Breitner > mail at joachim-breitner.de > http://www.joachim-breitner.de/ > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee -- Chris Allen Currently working on http://haskellbook.com From sandy at sandymaguire.me Fri Sep 21 14:13:55 2018 From: sandy at sandymaguire.me (Sandy Maguire) Date: Fri, 21 Sep 2018 14:13:55 -0000 Subject: [ghc-steering-committee] Please Review: Show Types as Symbols (#164), Shepherd: Richard Eisenberg In-Reply-To: <076c8de4d3619c45139494cdb61f7c9fb50c579a.camel@joachim-breitner.de> References: <076c8de4d3619c45139494cdb61f7c9fb50c579a.camel@joachim-breitner.de> Message-ID: Gentle ping on this! On Fri, Sep 7, 2018 at 3:54 PM, Joachim Breitner wrote: > Dear Committee, > > this is your secretary speaking: > > Provide a primitive to show types as Symbols, by Sandy Maguirer, was proposed > https://github.com/ghc-proposals/ghc-proposals/pull/164 > > I propose Richard as the shepherd, he already showed interest in this proposal. > > Please reach consensus as described in > https://github.com/ghc-proposals/ghc-proposals#committee-process > I suggest you make a recommendation, in a new e-mail thread with the > proposal number in the subject, about the decision, maybe point out > debatable points, and assume that anyone who stays quiet agrees with > you. > > Thanks, > Joachim > -- > Joachim Breitner > mail at joachim-breitner.de > http://www.joachim-breitner.de/ > > > _______________________________________________ > ghc-steering-committee mailing list > ghc-steering-committee at haskell.org > https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee >