Changes between Version 42 and Version 43 of ReportABug


Ignore:
Timestamp:
Oct 15, 2018 3:25:39 PM (2 months ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReportABug

    v42 v43  
    1515 * '''Is it a bug at all?'''.  Take a look at the [http://haskell.org/haskellwiki/GHC/FAQ FAQ] and [http://www.haskell.org/ghc/docs/latest/html/users_guide/gone_wrong.html What to do when something goes wrong] from the GHC User's Guide, which will give you some guidance as to whether the behaviour you're seeing is really a bug or not.
    1616
    17  * '''Duplicate bug reports'''.  Please search for existing tickets on the [http://hackage.haskell.org/trac/ghc bug tracker] or [http://www.google.com/?q=site:ghc.haskell.org/trac/ghc/ticket%20 Google].  If your problem has already been reported, it saves time to have all the manifestations of the same bug gathered together.  If you get an error message from GHC, a good search key is usually the non-program-specific part of the error message.[[BR]][[BR]]
     17 * '''Duplicate bug reports'''.  Please search for existing tickets on the [http://hackage.haskell.org/trac/ghc bug tracker] (search box in top right hand corner) or [http://www.google.com/?q=site:ghc.haskell.org/trac/ghc/ticket%20 Google].  If your problem has already been reported, it saves time to have all the manifestations of the same bug gathered together.  If you get an error message from GHC, a good search key is usually the non-program-specific part of the error message.[[BR]][[BR]]
    1818 If you do find an existing ticket that seems to describe the same problem, then
    1919    * Add a comment that explains how it manifests for you, and add your description of how to reproduce it (see below)