[GHC] #3693: Show stack traces

[GHC]

#3693: Show stack traces
-------------------------------------+------------------------------------
        Reporter:  jpet              |            Owner:  Tarrasch
            Type:  feature request   |           Status:  new
        Priority:  normal            |        Milestone:  7.10.1
       Component:  Runtime System    |          Version:  6.10.4
      Resolution:                    |         Keywords:
Operating System:  Unknown/Multiple  |     Architecture:  Unknown/Multiple
 Type of failure:  None/Unknown      |       Difficulty:  Unknown
       Test Case:                    |       Blocked By:
        Blocking:                    |  Related Tickets:
-------------------------------------+------------------------------------

Comment (by simonpj):

 Simon M and I took a look today.  We added a few notes to the github thing
 ​https://github.com/scpmw/ghc/commit/d233ea4da0a5725d4d29a3fb68b9b8f7c9bc6d32
 #diff-8b5b79c6cb1af2b387fa2d814cd0d3f6R1638

 The major stumbling block is giving a really clear description of what
 each of the various predicates on ticks means: `tickishScoped`,
 `tickishSoftScoped`, `tickishCounts`, `tickishIsCode` etc.

 We might want to rename some of them.  Eg `tickisScoped` and
 `tickishSoftScoped` might be replaced by `canFloatCodeInsideThisTick` and
 `canFloatCodeOutsideThisTick`, perhaps.  Each call site has asks a
 question about the equivalence of two pieces of code, and the predicates
 should probably have an example drawn from every call site.  That might
 make the correct generalisation clear.

 Simon

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/3693#comment:67>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler