Send Beginners mailing list submissions to
        beginners@haskell.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
or, via email, send a message with subject or body 'help' to
        beginners-requ...@haskell.org

You can reach the person managing the list at
        beginners-ow...@haskell.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Beginners digest..."


Today's Topics:

   1. Re:  Haskell for Imperative Programmers (Ionuț G. Stan)


----------------------------------------------------------------------

Message: 1
Date: Tue, 10 Jul 2018 15:34:30 +0300
From: Ionuț G. Stan <ionut.g.s...@gmail.com>
To: beginners@haskell.org
Subject: Re: [Haskell-beginners] Haskell for Imperative Programmers
Message-ID: <f42168a8-458b-834d-2773-d0f97fcad...@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed

On 10/07/2018 15:19, Theodore Lief Gannon wrote:
> An intuition that really clicked for me is that in Haskell IO code, as 
> in all Haskell code, you are describing a pristine and perfectly inert 
> data structure. It happens to *represent* a set of imperative 
> instructions that the totally impure runtime environment can execute, 
> but that's not your problem!

Just like in Java :) I'm kinda trolling a bit, but if I spend all my dev 
time inside an IO monad of sorts, I don't find that to be much different 
than writing Java.


> On Tue, Jul 10, 2018, 4:55 AM Olivier Revollat <revol...@gmail.com 
> <mailto:revol...@gmail.com>> wrote:
> 
>     Thanks !
> 
>     Le mar. 10 juil. 2018 à 13:14, PY <aqua...@gmail.com
>     <mailto:aqua...@gmail.com>> a écrit :
> 
>         May be something like this?
> 
>         *Free monads* ("applicative" style/interpreting trees) and Effects:
> 
>         https://markkarpov.com/post/free-monad-considered-harmful.html
>         https://mmhaskell.com/blog/2017/11/20/eff-to-the-rescue
> 
>         *Arrows* (something like "flow"-style):
>         https://www.haskell.org/arrows/
>         http://tuttlem.github.io/2014/07/26/practical-arrow-usage.html
> 
> 
>         10.07.2018 12:22, Olivier Revollat wrote:
>>         Hi,
>>         I've been using imperative languages for 20 years now :)
>>
>>         I'm a beginner in haskell and I love the paradigm shift you
>>         feel when you come from imperative programming. I found
>>         interesting articles like :
>>         https://wiki.haskell.org/Haskell_IO_for_Imperative_Programmers
>>
>>         Do you have any other ressources like that ?
>>         I'm not looking for how to use haskell in imperative style
>>         (e.g. with "do" notation, ...) no no ! I'm looking articles
>>         who explain how NOT TO USE imperative style with haskell, and
>>         help thinking the paradigm shift ...
>>
>>         Thanks :)
>>
>>
>>
>>         _______________________________________________
>>         Beginners mailing list
>>         Beginners@haskell.org <mailto:Beginners@haskell.org>
>>         http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
> 
>         _______________________________________________
>         Beginners mailing list
>         Beginners@haskell.org <mailto:Beginners@haskell.org>
>         http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
> 
>     _______________________________________________
>     Beginners mailing list
>     Beginners@haskell.org <mailto:Beginners@haskell.org>
>     http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
> 
> 
> 
> _______________________________________________
> Beginners mailing list
> Beginners@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
> 


-- 
Ionuț G. Stan  |  http://igstan.ro  |  http://bucharestfp.ro


------------------------------

Subject: Digest Footer

_______________________________________________
Beginners mailing list
Beginners@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners


------------------------------

End of Beginners Digest, Vol 121, Issue 10
******************************************

Reply via email to