[GHC] #11366: Control.Exception.assert should perhaps take an implicit call stack
GHC
ghc-devs at haskell.org
Wed Jan 6 23:24:24 UTC 2016
#11366: Control.Exception.assert should perhaps take an implicit call stack
-------------------------------------+-------------------------------------
Reporter: bgamari | Owner:
Type: task | Status: new
Priority: normal | Milestone: 8.0.1
Component: Compiler | Version: 7.10.3
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
| Unknown/Multiple
Type of failure: None/Unknown | Test Case:
Blocked By: | Blocking:
Related Tickets: | Differential Rev(s):
Wiki Page: |
-------------------------------------+-------------------------------------
Comment (by gridaphobe):
We actually do this already, but it's `assertError` that checks the
assertion and gets the CallStack. GHC rewrites `assert` to `assertError`
unless optimizations are enabled; `assert` is just `const id`.
I suppose it would be consistent to give `assert` a CallStack too, but GHC
will (rightly) complain that it's unused.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/11366#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list