From simonpj at microsoft.com Thu Mar 15 22:52:47 2018 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Thu, 15 Mar 2018 22:52:47 +0000 Subject: The Haskell Report: who maintains it? Message-ID: Friends Does anyone know who, if anyone, feels responsible for committing updates to the Haskell 2010 Report? Who even has commit rights? There’s Frank’s pull request below, and I have another important typo to fix. Thanks Simon From: Frank Steffahn [mailto:notifications at github.com] Sent: 11 March 2018 17:03 To: haskell/haskell-report Cc: Subscribed Subject: [haskell/haskell-report] Fix a typo in: Semantics of Case Expressions, Part 3 (s) (#4) Hi. I noticed this in the Haskell 2010 report, which is an obvious typo / mistake. I’m not 100% sure if this is the right branch (or even in general the right place) to note this, but I hope it will get fixed ;-) This seems like it is an artifact of copy-and-pasting from “Semantics of Case Expressions, Part 1 (c)” without properly adapting the thing, especially in commit bc94554. ________________________________ You can view, comment on, or merge this pull request online at: https://github.com/haskell/haskell-report/pull/4 Commit Summary * Fix a typo in: Semantics of Case Expressions, Part 3 (s) File Changes * M report/exps.verb (1) Patch Links: * https://github.com/haskell/haskell-report/pull/4.patch * https://github.com/haskell/haskell-report/pull/4.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmct at jmct.cc Thu Mar 15 23:17:12 2018 From: jmct at jmct.cc (=?utf-8?Q?Jos=C3=A9=20Manuel=20Calder=C3=B3n=20Trilla?=) Date: Thu, 15 Mar 2018 19:17:12 -0400 Subject: [Haskell] The Haskell Report: who maintains it? In-Reply-To: References: Message-ID: <1521155832.1278526.1304854160.6717D8AD@webmail.messagingengine.com> All of us on the Haskell Language Committee have the ability to commit on that repo. I think typos are uncontroversial and I'll happily merge pull requests like that. I think the pull-request you point out suffered from the bystander effect, unfortunately. I'll review and merge it now. If you let me know the typo you'd like fixed I'll make sure that gets done as well. Cheers,José Manuel On Thu, Mar 15, 2018, at 6:52 PM, Simon Peyton Jones via Haskell wrote:> Friends > > Does anyone know who, if anyone, feels responsible for committing > updates to the Haskell 2010 Report?> > Who even has commit rights? > > There’s Frank’s pull request below, and I have another important > typo to fix.> > Thanks > > Simon > > > *From:* Frank Steffahn [mailto:notifications at github.com] *Sent:* 11 > March 2018 17:03 *To:* haskell/haskell-report report at noreply.github.com> *Cc:* Subscribed > *Subject:* [haskell/haskell-report] > Fix a typo in: Semantics of Case Expressions, Part 3 (s) (#4)> > Hi. I noticed this in the Haskell 2010 report, which is an obvious > typo / mistake. I’m not 100% sure if this is the right branch (or > even in general the right place) to note this, but I hope it will get > fixed ;-)> This seems like it is an artifact of copy-and-pasting from “Semantics > of Case Expressions, Part 1 (c)” without properly adapting the thing, > especially in commit bc94554.> > You can view, comment on, or merge this pull request online at: > https://github.com/haskell/haskell-report/pull/4[1] > Commit Summary > * Fix a typo in: Semantics of Case Expressions, Part 3 (s)> File Changes > * *M* report/exps.verb[2] (1) > Patch Links: > * https://github.com/haskell/haskell-report/pull/4.patch[3] > * https://github.com/haskell/haskell-report/pull/4.diff[4]> — You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub[5], or mute the > thread[6].> _________________________________________________ > Haskell mailing list > Haskell at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell Links: 1. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhaskell%2Fhaskell-report%2Fpull%2F4&data=04%7C01%7Csimonpj%40microsoft.com%7C31eff0e0f0104cb0e64408d58771f2eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636563845832254992%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=1xk6eQn%2Fq4vKglbQSLHNOGYrNdxJBp074b2%2ByJbvCrQ%3D&reserved=0 2. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhaskell%2Fhaskell-report%2Fpull%2F4%2Ffiles%23diff-0&data=04%7C01%7Csimonpj%40microsoft.com%7C31eff0e0f0104cb0e64408d58771f2eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636563845832254992%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=OYptlGmxyWflETFlpd4f8ln1AEYgT8EwiYX44dPafJI%3D&reserved=0 3. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhaskell%2Fhaskell-report%2Fpull%2F4.patch&data=04%7C01%7Csimonpj%40microsoft.com%7C31eff0e0f0104cb0e64408d58771f2eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636563845832254992%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=gUICTD38nmiLSOheLW14zHM%2FTj2Uv59k7kxyxXKXgpU%3D&reserved=0 4. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhaskell%2Fhaskell-report%2Fpull%2F4.diff&data=04%7C01%7Csimonpj%40microsoft.com%7C31eff0e0f0104cb0e64408d58771f2eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636563845832254992%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=NrCOwM0rJ8rH0p7d3tSG7YCsVziBJGli%2BKfx8SaFgDE%3D&reserved=0 5. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhaskell%2Fhaskell-report%2Fpull%2F4&data=04%7C01%7Csimonpj%40microsoft.com%7C31eff0e0f0104cb0e64408d58771f2eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636563845832254992%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=1xk6eQn%2Fq4vKglbQSLHNOGYrNdxJBp074b2%2ByJbvCrQ%3D&reserved=0 6. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAjsewyB3mgR1zjDxYvon2hz67U0hf_Zks5tdVjEgaJpZM4SlxDs&data=04%7C01%7Csimonpj%40microsoft.com%7C31eff0e0f0104cb0e64408d58771f2eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636563845832254992%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=mnTU7w1yzqPGoT6eYBrw21SvvrnH6byxUEi2yZZ1ftE%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From simonpj at microsoft.com Mon Mar 19 13:29:42 2018 From: simonpj at microsoft.com (Simon Peyton Jones) Date: Mon, 19 Mar 2018 13:29:42 +0000 Subject: Haskell Report 2010: pattern bindings Message-ID: Thanks Jose. The other issue I have in mind is that of pattern bindings. Currently in the 2010 Haskell Report * The text on the monomorphism restriction (4.5.5) refers to “simple pattern bindings”. * It claims that a simple pattern binding “is a pattern binding in which the pattern consists of a single variable” * You’d expect “simple pattern binding” to be defined in 3.17.1 Patterns. But it isn’t. * Instead, 4.4.3.2 Pattern bindings explicitly contradicts 4.5.5 by saying “a simple pattern binding has form p=e”. What a mess! The simplest way out is probably: * Define “simple pattern binding” to be of form x=e, in 3.17.1. * Fix the first para of 4.4.3.2. * Fix the cross-ref in 4.5.5 to refer to the definition of simple pattern. Sadly, 4.4.3.2 still is not very well defined. It’s supposed to say what pattern bindings mean, including top-level ones; but it does so by referring to 3.12 which does not handle top-level bindings. I’m not sure if this is worth fixing. Simon From: José Manuel Calderón Trilla Sent: 15 March 2018 23:17 To: Simon Peyton Jones ; haskell-prime at haskell.org; ghc-devs at haskell.org Subject: Re: [Haskell] The Haskell Report: who maintains it? All of us on the Haskell Language Committee have the ability to commit on that repo. I think typos are uncontroversial and I'll happily merge pull requests like that. I think the pull-request you point out suffered from the bystander effect, unfortunately. I'll review and merge it now. If you let me know the typo you'd like fixed I'll make sure that gets done as well. Cheers, José Manuel On Thu, Mar 15, 2018, at 6:52 PM, Simon Peyton Jones via Haskell wrote: Friends Does anyone know who, if anyone, feels responsible for committing updates to the Haskell 2010 Report? Who even has commit rights? There’s Frank’s pull request below, and I have another important typo to fix. Thanks Simon From: Frank Steffahn [mailto:notifications at github.com] Sent: 11 March 2018 17:03 To: haskell/haskell-report Cc: Subscribed Subject: [haskell/haskell-report] Fix a typo in: Semantics of Case Expressions, Part 3 (s) (#4) Hi. I noticed this in the Haskell 2010 report, which is an obvious typo / mistake. I’m not 100% sure if this is the right branch (or even in general the right place) to note this, but I hope it will get fixed ;-) This seems like it is an artifact of copy-and-pasting from “Semantics of Case Expressions, Part 1 (c)” without properly adapting the thing, especially in commit bc94554. ________________________________ You can view, comment on, or merge this pull request online at: https://github.com/haskell/haskell-report/pull/4 Commit Summary * Fix a typo in: Semantics of Case Expressions, Part 3 (s) File Changes * M report/exps.verb (1) Patch Links: * https://github.com/haskell/haskell-report/pull/4.patch * https://github.com/haskell/haskell-report/pull/4.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread. _______________________________________________ Haskell mailing list Haskell at haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 332 bytes Desc: image001.jpg URL: From gershomb at gmail.com Sat Mar 24 16:22:41 2018 From: gershomb at gmail.com (Gershom B) Date: Sat, 24 Mar 2018 12:22:41 -0400 Subject: Place to report non-textual (markup) issues on the haskell report? Message-ID: In reviewing tickets, I noticed the following: https://github.com/haskell-infra/hl/issues/172 This is not an issue about the haskell homepage, but about the markup of the report, with some suggestions on how to make it easier to navigate. The github repo for the report does not seem to have “issues” turned on — I suppose to discourage filing issues against the report itself, for which there is a different process. Nonetheless, I would like to get this information captured in some appropriate place/way. I added a label for `haskell-report` to the issue, which I guess is a start. Further suggestions? —Gershom -------------- next part -------------- An HTML attachment was scrubbed... URL: From blamario at ciktel.net Mon Mar 26 01:10:05 2018 From: blamario at ciktel.net (=?UTF-8?Q?Mario_Bla=c5=beevi=c4=87?=) Date: Sun, 25 Mar 2018 21:10:05 -0400 Subject: Place to report non-textual (markup) issues on the haskell report? In-Reply-To: References: Message-ID: Related to this, whatever happened to the fully-agreed task of copying the Haskell report LaTeX files over to the RFCs repository? https://mail.haskell.org/pipermail/haskell-prime/2017-September/004319.html https://mail.haskell.org/pipermail/haskell-prime/2017-October/thread.html https://mail.haskell.org/pipermail/haskell-prime/2017-November/thread.html On 2018-03-24 12:22 PM, Gershom B wrote: > In reviewing tickets, I noticed the following: > https://github.com/haskell-infra/hl/issues/172 > > This is not an issue about the haskell homepage, but about the markup > of the report, with some suggestions on how to make it easier to navigate. > > The github repo for the report does not seem to have “issues” turned > on — I suppose to discourage filing issues against the report itself, > for which there is a different process. > > Nonetheless, I would like to get this information captured in some > appropriate place/way. I added a label for `haskell-report` to the > issue, which I guess is a start. > > Further suggestions? > > —Gershom > > > > _______________________________________________ > Haskell-prime mailing list > Haskell-prime at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-prime