Thanks. the instructions are really out of date. Now that so many of us work on GHC, it's too easy for an email to get lost. Trac is better. I'll update the instructions!
S From: ghc-devs [mailto:[email protected]] On Behalf Of Pedro Rodrigues Sent: 05 November 2013 21:47 To: Carter Schonwald Cc: [email protected] Subject: Re: [PATCH] Fix typo in User's Guide Sure, here it is http://ghc.haskell.org/trac/ghc/ticket/8505 Should every bug fix have an associated ticket? Because from the instructions on Trac<http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/FixingBugs>, I got the impression that for quick fixes it was not necessary to create a ticket. Cheers, Pedro Rodrigues On 5 November 2013 18:56, Carter Schonwald <[email protected]<mailto:[email protected]>> wrote: could you file a ticket on trac with the patch? On Tue, Nov 5, 2013 at 6:27 AM, Pedro Rodrigues <[email protected]<mailto:[email protected]>> wrote: --- docs/users_guide/glasgow_exts.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/docs/users_guide/glasgow_exts.xml b/docs/users_guide/glasgow_exts.xml index ce07806..d61ff7a 100644 --- a/docs/users_guide/glasgow_exts.xml +++ b/docs/users_guide/glasgow_exts.xml @@ -8673,7 +8673,7 @@ proc (x,y) -> which is translated to <screen> arr (\ (x,y) -> if f x y then Left x else Right y) >>> - (arr (\x -> x+1) >>> f) ||| (arr (\y -> y+2) >>> g) + (arr (\x -> x+1) >>> g) ||| (arr (\y -> y+2) >>> h) </screen> Since the translation uses <function>|||</function>, the arrow concerned must belong to the <literal>ArrowChoice</literal> class. -- 1.7.4.1 _______________________________________________ ghc-devs mailing list [email protected]<mailto:[email protected]> http://www.haskell.org/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list [email protected] http://www.haskell.org/mailman/listinfo/ghc-devs
