[GHC] #14266: AllowAmbiguousTypes doesn't play well with default class methods

[GHC]

#14266: AllowAmbiguousTypes doesn't play well with default class methods
-------------------------------------+-------------------------------------
        Reporter:  chris-martin      |                Owner:  (none)
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Compiler          |              Version:  8.0.2
      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 chris-martin):

 Replying to [comment:6 RyanGlScott]:
 > but now that it's an established thing, the scope of what's considered
 "reasonable" code has increased drastically.

 I suppose that's something I'm not clear on. What is the language
 designers' attitude toward the `TypeApplications` extension? Is it there
 to be an imperfect workaround for the occasional odd situation, or is
 Haskell now intended to be a language where programming with ambiguous
 types is normal and fully supported?

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