[GHC] #8026: DatatypeContexts should be fixed, not deprecated
GHC
ghc-devs at haskell.org
Wed Sep 24 12:07:33 UTC 2014
#8026: DatatypeContexts should be fixed, not deprecated
-------------------------------------+-------------------------------------
Reporter: gidyn | Owner:
Type: feature | Status: closed
request | Milestone:
Priority: normal | Version: 7.6.3
Component: Compiler | Keywords:
Resolution: wontfix | Architecture: Unknown/Multiple
Operating System: | Difficulty: Unknown
Unknown/Multiple | Blocked By:
Type of failure: | Related Tickets:
None/Unknown |
Test Case: |
Blocking: |
Differential Revisions: |
-------------------------------------+-------------------------------------
Changes (by goldfire):
* status: new => closed
* resolution: => wontfix
Comment:
I'm afraid the recent salvo of examples has done little to convince me of
what this extension really means. The only I can glean from this is you
want a very syntactic translation of a type `... HasEq a ...` to `Eq a =>
... HasEq a ...`. The problem is that this translation doesn't always make
sense, given the other features of Haskell's type system, and would either
work or not work in various scenarios unpredictably.
At the risk of repeating myself: those of us with experience working
inside GHC and who do know type theory think this proposal doesn't fly. We
love contributions and ideas from folks without this experience. But, in
this case, where we disagree with the proposal, the burden rests on the
proposers to convince us that the proposal holds water. The way to do this
starts with a wiki page and typing rules, not just examples.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8026#comment:23>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list