caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Philippe Veber <philippe.veber@gmail.com>
To: Oleg <oleg@okmij.org>, Philippe Veber <philippe.veber@gmail.com>,
	 caml users <caml-list@inria.fr>,
	"Richard W.M. Jones" <rich@annexia.org>,
	nick.palladinos@gmail.com
Subject: Re: [Caml-list] What if exn was not an open type?
Date: Sat, 4 Nov 2017 18:52:30 +0100	[thread overview]
Message-ID: <CAOOOohT7B4fFgyNEVja0EBpHaioM-X+YxZUESeDZq+gsZJ1UGg@mail.gmail.com> (raw)
In-Reply-To: <20171101071609.GA1448@Magus.localnet>

[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]

Thanks a lot Leo and Oleg for all this very exciting material!

2017-11-01 8:16 GMT+01:00 Oleg <oleg@okmij.org>:

>
>
> > I thought one big selling argument of monads was also that the type of
> > the functions shows which effect it performs. As I understand it, it
> > is not the case for effects, at least not in existing implementations
> > like multicore ocaml. ... Also, would you know a reference that shows
> > that effects compose indeed a lot more easily than monads?
>
> How expressive are the types of effectful computations pretty much
> depends on a particular type system in use. Let me cite from the message
> that I received from Nick Palladinos (CCed) the other week, who implemented
> extensible effects in F#, a rather close relative of OCaml. You can
> write the code as below
>
> let example () =
>     eff {
>         do! put 1
>         let! x = get ()
>         let! y = ask ()
>         return x + y
>     }
>
> (Here, `eff' is a tag of so-called computational expressions of F#, a
> very handy feature).
>
> The *inferred* type is as follows
>   val example : unit -> Eff<'U,int> when 'U :> Reader<int> and 'U :>
> State<int>
>
> clearly stating that example is an effectful expression that uses at
> least Reader and State effects. The example also illustrates
> composability, your second question: put/get and ask are operations of two
> distinct effects (State and Reader, resp). You can combine them freely
> within the same program.
>
> (I hope Nick will write a paper explaining his implementation so that
> we can all learn from it.)
>
> To give more references (in addition to Leo's work), I should point to Koka
>         https://koka-lang.github.io/koka/doc/kokaspec.html
>
> which is an OCaml-like language based on effects and
> effect-typing. The language is mature enough to write a web server in
> it (as Daan Leijen described in his talk at the ML Family workshop
> this year).
>
>         Other references are the recent Effekt library in Scala
>         http://b-studios.de/scala-effekt/
>         and extensible-effect library
>         http://okmij.org/ftp/Haskell/extensible/
> which, although being first proposed for Haskell has also been ported
> to Scala (and now F#). Purescript's extensible effects are also
> similar.
>
>
>

[-- Attachment #2: Type: text/html, Size: 3176 bytes --]

  reply	other threads:[~2017-11-04 17:52 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20  9:56 Malcolm Matalka
2017-10-20 10:55 ` David Allsopp
2017-10-20 11:21   ` Ivan Gotovchits
2017-10-20 11:38     ` Simon Cruanes
2017-10-20 16:54       ` Malcolm Matalka
2017-10-20 19:47         ` Simon Cruanes
2017-10-21 21:15           ` Malcolm Matalka
2017-10-24 13:30       ` Richard W.M. Jones
2017-10-24 19:02         ` Petter A. Urkedal
2017-11-04 18:44           ` Richard W.M. Jones
2017-11-04 18:48             ` SP
2017-11-04 18:53               ` Richard W.M. Jones
2017-11-04 19:03                 ` SP
2017-11-04 19:01             ` Max Mouratov
2017-11-04 19:16             ` octachron
2017-11-05 17:41               ` Richard W.M. Jones
2017-11-05 18:39                 ` Yaron Minsky
2017-11-05 20:49                   ` Gabriel Scherer
2017-11-05 21:48                     ` Yaron Minsky
2017-11-05 21:53                     ` Petter A. Urkedal
2017-11-05 18:02             ` Petter A. Urkedal
2017-11-05 18:24               ` Richard W.M. Jones
2017-11-05 18:55                 ` Petter A. Urkedal
     [not found]         ` <CALa9pHQ-nhWf4T0U5gDiKTduPiEeXSZPQ=DY6N1YNbCXqRohPQ@mail.gmail.com>
2017-10-25  8:35           ` Richard W.M. Jones
2017-10-25  9:12             ` Philippe Veber
2017-10-25 14:52               ` Richard W.M. Jones
2017-10-25 16:37                 ` Ivan Gotovchits
2017-10-25 17:47                   ` SP
2017-10-26  8:06                 ` Malcolm Matalka
2017-10-26  8:11                   ` Xavier Leroy
2017-10-25 13:36             ` Ivan Gotovchits
2017-10-26  7:31             ` Petter A. Urkedal
2017-10-27 13:58             ` Oleg
2017-10-27 14:24               ` Philippe Veber
2017-10-27 14:49                 ` Leo White
2017-11-01  7:16                 ` Oleg
2017-11-04 17:52                   ` Philippe Veber [this message]
2017-10-20 17:07   ` Malcolm Matalka
2017-10-21 21:28 ` Nathan Moreau
2017-10-22 12:39   ` Malcolm Matalka
2017-10-22 13:08     ` Nathan Moreau
2017-10-24 11:11     ` SP
2017-10-24 11:16       ` Gabriel Scherer
2017-10-25 11:30         ` Malcolm Matalka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOOOohT7B4fFgyNEVja0EBpHaioM-X+YxZUESeDZq+gsZJ1UGg@mail.gmail.com \
    --to=philippe.veber@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=nick.palladinos@gmail.com \
    --cc=oleg@okmij.org \
    --cc=rich@annexia.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).