The Haskell Report: who maintains it?

2018-03-15 Thread Simon Peyton Jones via ghc-devs 
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:notificati...@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.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [Haskell] The Haskell Report: who maintains it?

2018-03-15 Thread David Feuer 
We also have an inconsistency between the textual descriptions of
accumArray and accum and their reference implementations. I recently
changed GHC's implementations to better match the text (for efficiency
reasons), but the reference implementations should be adjusted too.

On Thu, Mar 15, 2018 at 6:52 PM, Simon Peyton Jones via Haskell <
hask...@haskell.org> 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:notificati...@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
> hask...@haskell.

Re: [Haskell] The Haskell Report: who maintains it?

2018-03-15 Thread José Manuel Calderón Trilla 
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:notificati...@github.com] *Sent:* 11
> March 2018 17:03 *To:* haskell/haskell-report  rep...@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
> hask...@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
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Custom ghcPrimIface for cross-compilation?

2018-03-15 Thread Shao Cheng 
Hi all, is it possible for a 64-bit ghc to emit 32-bit code, if I supply a
custom ghcPrimIface via Hooks and also modify the platform flags in
DynFlags? The module does not import Prelude and has no dependencies other
than GHC.Prim.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Custom ghcPrimIface for cross-compilation?

2018-03-15 Thread Moritz Angermann 
Hi,

not sure I understand your question. If you build a cross compiler
targetting a 32bit device (say Raspbian/Raspberry Pi) for say x86_64
linux, you end up with a 64bit compiler emitting code for a 32bit
device.

If you question revolves around dynamically changing GHCs target at
runtime.  Essentially turning GHC into a multi-target compiler, we
hope to get there eventually.

Please not that just emitting a single module in 32bit is likely not
going to get you far. You will still need to build the rts and potentially
some additional support libraries to turn that module into something
useful.

Cheers,
 Moritz

> On Mar 16, 2018, at 1:12 PM, Shao Cheng  wrote:
> 
> Hi all, is it possible for a 64-bit ghc to emit 32-bit code, if I supply a 
> custom ghcPrimIface via Hooks and also modify the platform flags in DynFlags? 
> The module does not import Prelude and has no dependencies other than 
> GHC.Prim. ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs