#11398: Type application for operator sections -------------------------------------+------------------------------------- Reporter: Iceland_jack | Owner: Type: feature request | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.10.3 Resolution: | Keywords: | TypeApplications 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 goldfire): What's the typing rule you're proposing? It's awfully easy to find cases like this one where the behavior is straightforward, but coming up with a consistent rule is quite hard. Take `const`. What type should {{{(`const` undefined)}}} have? `forall a. a -> a`? `forall a b. a -> a`? What about {{{(undefined `const`)}}}? In the end, I think this is a no-go, for exactly the same reason that applied functions have inferred type parameters, not specified ones. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/11398#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler