From: Gregory Malecha <gmalecha@gmail.com>
To: "Ben Millwood" <bmillwood@janestreet.com>,
"Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
Jonas Jensen <jj@issuu.com>,
Yaron Minsky <yminsky@janestreet.com>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Question about Optimization
Date: Fri, 22 Apr 2016 09:09:55 -0700 [thread overview]
Message-ID: <CAGraiHLRazLL6x-ep_J_7xBmZ71Afmz00w2ncDPx75uPzLtfXA@mail.gmail.com> (raw)
In-Reply-To: <CA+MHO51+TVda4SkML4=3m6tao+G7oTm8Z6idymLUohDqZmLawg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
Hi, Ben --
Thanks this is really helpful.
On Thu, Apr 21, 2016, 9:35 AM Ben Millwood <bmillwood@janestreet.com> wrote:
> You can see hints at the problems with rewrite rules by reading about the
> mechanisms GHC has to work around them:
>
>
> https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/pragmas.html#inline-pragma
>
> For example, rules can be prevented from matching if some subexpression is
> inlined first, but on the flipside, some rules need some inlining to occur
> before they can match. This leads GHC to support "phase specifications"
> that help you to control the order of inlinings and rules.
>
> On 21 April 2016 at 12:05, Daniel Bünzli <daniel.buenzli@erratique.ch>
> wrote:
>
>> Le jeudi, 21 avril 2016 à 18:02, Gabriel Scherer a écrit :
>> > useful in some situations but also very fragile.
>>
>> What kind of fragility ?
>>
>> Daniel
>>
> --
>> 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: 2551 bytes --]
next prev parent reply other threads:[~2016-04-22 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 7:13 Gregory Malecha
2016-04-21 9:32 ` Jonas Jensen
2016-04-21 11:45 ` Yaron Minsky
2016-04-21 15:45 ` Gregory Malecha
2016-04-21 16:02 ` Gabriel Scherer
2016-04-21 16:05 ` Daniel Bünzli
2016-04-21 16:35 ` Ben Millwood
2016-04-22 16:09 ` Gregory Malecha [this message]
2016-11-08 12:07 ` [Caml-list] The fastest stream library [Was: Question about Optimization] Oleg
2016-11-08 12:05 ` Gregory Malecha
2016-11-08 12:15 ` Gabriel Scherer
2016-11-08 12:47 ` [Caml-list] The fastest stream library [Was: Question about Oleg
2016-11-08 15:45 ` Gabriel Scherer
2016-11-12 13:01 ` Oleg
2016-11-12 16:21 ` Simon Cruanes
2016-11-12 16:35 ` Gabriel Scherer
-- strict thread matches above, loose matches on Subject: below --
2008-11-02 2:52 Question about optimization Michał C
2008-11-02 12:23 ` [Caml-list] " Peng Zang
2008-11-02 13:02 ` Jon Harrop
2008-11-02 15:52 ` Jon Harrop
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=CAGraiHLRazLL6x-ep_J_7xBmZ71Afmz00w2ncDPx75uPzLtfXA@mail.gmail.com \
--to=gmalecha@gmail.com \
--cc=bmillwood@janestreet.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
--cc=gabriel.scherer@gmail.com \
--cc=jj@issuu.com \
--cc=yminsky@janestreet.com \
/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).