Re: Enabling TypeHoles by default

>> it can >> > break anything. >> > >> > Отправлено с iPad >> > >> > 13 янв. 2014 г., в 22:54, Edward Kmett написал(а): >> > >> > I have to admit, I rather like this suggestion. >> > >> > -Edward >> &

Enabling TypeHoles by default

Hello, As discussed on ghc-devs, I propose to enable -XTypeHoles in GHC by default. Rationale: (1) This way holes are far easier to use; just entering "_" allows to check type of a subexpression, no need of adding "-XTypeHoles". (2) This affects error messages only; i.e. the set of programs that

Re: TypeHoles behaviour

I have also seen this behaviour and support the change. -KG 2013/8/27 Austin Seipp > I'm +1 on changing the behavior. I find it probably the most confusing > aspect of using TypeHoles, which is otherwise great. > > On Tue, Aug 27, 2013 at 3:17 AM, Simon Peyton-Jones > wrote: > > I'm sympathetic

Re: implicit params in instance contexts

GHC ticket: http://ghc.haskell.org/trac/ghc/ticket/7624 2013/7/16 Ganesh Sittampalam > Hi, > > It seems that from GHC 7.4, the prohibition on implicit parameter > constraints in instance declarations has been relaxed. The program below > gives the error "Illegal constraint ?fooRev::Bool" in GHC