#9883: Make OverloadedLists more usable by splitting the class interface -------------------------------------+------------------------------------- Reporter: muesli4 | Owner: Type: feature | Status: closed request | Milestone: ⊥ Priority: normal | Version: 7.8.3 Component: External | Keywords: overloaded lists, Core | islist Resolution: duplicate | Architecture: Unknown/Multiple Operating System: | Difficulty: Moderate (less Unknown/Multiple | than a day) Type of failure: | Blocked By: 7495 None/Unknown | Related Tickets: #7495 Test Case: | Blocking: | Differential Revisions: | -------------------------------------+------------------------------------- Comment (by simonpj): I'm far from sure that it's a dup of #7495, so I'm reopening. This ticket has a clear proposal; #7495 does not. By all means go ahead and forge a consensus about this ticket. I wonder if `IsList` could be a superclass of `AsList`? That is, do you want to be able to pattern-match on a list-like thing, but not be able to use literals for that type? Or are they best considered as orthogonal? The nomenclature clearly needs fixing! Simon -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/9883#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler