Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Arnaud Spiwack <aspiwack@lix.polytechnique.fr>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: OCaML Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Purity in ocaml
Date: Tue, 28 Jan 2014 10:21:20 +0100	[thread overview]
Message-ID: <CAMoPVjcbiG=b2D+q2LV5LRjaV2c17VOOocFkOQ4w2Df+v-zoKg@mail.gmail.com> (raw)
In-Reply-To: <20140127093204.GA24902@frosties>

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

> Do you mean something like this?
>
> let g = function 0 -> raise G | n -> n
> let f = function 1 -> raise F | n -> n
>
> map f (map g [1;0]) ===> raise G
> map (f %> g) [1;0]  ===> raise F
>
> It is true, the exception prevents any optimization that would reorder
> two functions that both throw an excepition.


Precisely


> But many other
> optimizations are still possible, e.g. common subexpression
> elimination:
>
> let n =
>   let x = f (g 1) in
>   let y = g 1 in
>   x + y
>
> ==>
>
> let n =
>   let t = g 1 in
>   let x = f t in
>   let y = t in
>   x + y
>

To some degree:

let n =
  let x = f (g 1) (h ()) in
  let y = g 1 in
  x+y

is a different program than

let n =
  let t = g 1 in
  let x = f t (h ()) in
  let y = t in
  x+y

As it reorders (g 1) and (h ()). I think the rule is something like: when
the program is in monadic form, and you have a call to e, you can factor in
every subsequent calls to e. Which I guess is good enough. But I would tend
to believe deforestation would be tremendously more useful than common
expression elimination.


>
> MfG
>         Goswin
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>

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

  reply	other threads:[~2014-01-28  9:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 20:45 Yotam Barnoy
2014-01-20 21:08 ` Siraaj Khandkar
2014-01-20 21:16   ` Yotam Barnoy
2014-01-20 21:31     ` Siraaj Khandkar
2014-01-20 21:43       ` Yotam Barnoy
2014-01-20 22:55         ` Siraaj Khandkar
2014-01-21  1:37           ` Yotam Barnoy
2014-01-21  9:49 ` Goswin von Brederlow
2014-01-21 15:27   ` Yotam Barnoy
2014-01-23  9:20     ` Goswin von Brederlow
2014-01-23  9:35       ` Arnaud Spiwack
2014-01-27  9:32         ` Goswin von Brederlow
2014-01-28  9:21           ` Arnaud Spiwack [this message]
2014-02-01 14:52             ` Goswin von Brederlow
2014-02-03  9:20               ` Arnaud Spiwack
2014-01-23 18:18       ` Yotam Barnoy
2014-01-27  9:46         ` Goswin von Brederlow
2014-01-29 17:16           ` Yotam Barnoy
2014-02-01 15:03             ` Goswin von Brederlow

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='CAMoPVjcbiG=b2D+q2LV5LRjaV2c17VOOocFkOQ4w2Df+v-zoKg@mail.gmail.com' \
    --to=aspiwack@lix.polytechnique.fr \
    --cc=caml-list@inria.fr \
    --cc=goswin-v-b@web.de \
    /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