Applicative Comprehensions

2015-10-12 Thread David A Roberts
Hi, I raised this question on #haskell, and was advised that this was probably the best place to discuss. I see that Applicative Do is scheduled for GHC 8.0 [1], and was hoping that this might also enable support for Applicative Comprehensions [2]. Is this likely to be the case? If not, would it

Re: Applicative Comprehensions

2015-10-12 Thread Joachim Breitner
Hi, Am Montag, den 12.10.2015, 08:09 + schrieb David A Roberts: > I understand that comprehensions tend not to be used much in > idiomatic Haskell, quite contrary! I use them extensively in real-world-projects, and I claim to write idomatic code :-) Greetings, Joachim -- Joachim “nomeata”

RE: Applicative Comprehensions

2015-10-12 Thread Simon Peyton Jones
Sounds reasonable to me. Do-notation and comprehension notation are really just syntactic sugar for the same thing. Simon From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of David A Roberts Sent: 12 October 2015 09:10 To: ghc-devs@haskell.org Subject: Applicative Comprehensions

Re: Applicative Comprehensions

2015-10-12 Thread Roman Cheplyaka
I like this idea because having the pure function call at the beginning (rather than at the end, as with do-notation) is more consistent with the original <$>,<*>-notation. It only slightly bothers me that the bracket notation in this form has nothing to do with lists, so that may be a bit conf

Re: Applicative Comprehensions

2015-10-12 Thread Oleg Grenrus
Paralell comprehension syntax will be confusing. If user have both MonadComprehensions and ApplicativeDo enabled, it makes total sense to desugar monad comprehensions into Applicative expression when it’s possible, and into Monadic otherwise. I’m actually a bit surprised if it’s not already a c

Strictness/demand analysis without worker/wrapper, or, reviving -fmax-worker-args

2015-10-12 Thread Christiaan Baaij
Hi, As a GHC API user, I would like to run GHC’s strictness and demand analysis pass, but I don’t want any worker/wrappers. My specific use-case is to generate digital circuits from Haskell code, where I’ve yet to encounter any benefit from worker/wrappers: the generated circuits do not get any

"Excuse me, I think this i my stop..." - Resigning from the Platform

2015-10-12 Thread Mark Lentczner
I think this is the right time for me to exit: The truth is, I still can't bring myself to use a version of Haskell post the Foldable-Traversable-aPocalypse, let alone some future Haskell after the changes now in the works. My personal machines are all still 7.8. My personal projects are all pre-F

Re: "Excuse me, I think this i my stop..." - Resigning from the Platform

2015-10-12 Thread Gershom B
Thanks Mark for all your work over the years! Haskell has the adoption it does today in no small part because of your work in making sure it has been consistently easy to install over a range of systems. You’ve put many years and long hours into the work you’ve done as release manager, and we al