[GHC] #11760: runST with lazy blackholing breaks referential transparency
GHC
ghc-devs at haskell.org
Tue Mar 29 11:12:07 UTC 2016
#11760: runST with lazy blackholing breaks referential transparency
-------------------------------------+-------------------------------------
Reporter: Yuras | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
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: |
-------------------------------------+-------------------------------------
Changes (by simonpj):
* cc: simonmar, rnewton (added)
Comment:
This looks bad. Do you have a more detailed theory? Our thinking about
lazy blackholing is that if two threads start to evaluate the same thunk,
they may waste work but shoudl still get the same value. But that is not
happening here and I'd like to understand why.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/11760#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list