From: Yawar Amin <yawar.amin@gmail.com>
To: Marshall <marshall@logical.net>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] ReasonML concrete syntax
Date: Wed, 13 Dec 2017 11:44:54 -0500 [thread overview]
Message-ID: <CAJbYVJKE7tf_GNKLFR=xF8V7nGcVh3s1yAtnmO_OOi8W90fOZw@mail.gmail.com> (raw)
In-Reply-To: <7BE82AAB-9F65-49E4-B9A8-69FCC5719253@logical.net>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
In the second example, the second `print_int` never gets called.
On Wed, Dec 13, 2017 at 11:38 AM, Marshall <marshall@logical.net> wrote:
>
> > On Dec 13, 2017, at 4:37 AM, David Allsopp <dra-news@metastack.com>
> wrote:
> >
> > In terms of why you might want to be "hiding" currying, or at least
> making it need less immediate explanation when learning the language,
> consider, for example, explaining the difference between:
> >
> > let f x y = print_int x; print_int y in
> > f 42
> >
> > and
> >
> > let f x = print_int x; print_int in
> > f 42
>
> Apart from ReasonML, this is interesting. Why do these behave
> differently? I don’t understand yet.
>
>
>
> --
> 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: 1700 bytes --]
next prev parent reply other threads:[~2017-12-13 16:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 18:12 Robert Muller
2017-12-11 0:09 ` Yawar Amin
2017-12-11 5:50 ` Viet Le
2017-12-11 6:45 ` Ian Zimmerman
2017-12-11 6:53 ` Sven SAULEAU
2017-12-11 6:50 ` Sven SAULEAU
2017-12-11 6:54 ` Evgeny Khramtsov
2017-12-11 7:22 ` =?gb18030?B?Qm9i?=
2017-12-11 7:16 ` Evgeny Khramtsov
2017-12-17 15:02 ` Paolo Donadeo
2017-12-17 16:01 ` Guillaume Huysmans
2017-12-17 16:55 ` Paolo Donadeo
2017-12-17 20:13 ` Ian Zimmerman
2017-12-17 20:49 ` Robert Muller
2017-12-18 1:34 ` Yawar Amin
2017-12-18 16:36 ` Evgeny Khramtsov
2017-12-18 17:00 ` Jesper Louis Andersen
2017-12-18 17:27 ` Gary Trakhman
2017-12-18 17:53 ` Evgeny Khramtsov
2017-12-18 2:14 ` Yawar Amin
2017-12-11 15:51 ` Yawar Amin
2017-12-11 16:07 ` Sven SAULEAU
2017-12-11 17:11 ` David Brown
2017-12-12 3:49 ` Louis Roché
2017-12-12 4:18 ` Yawar Amin
2017-12-12 5:52 ` Oliver Bandel
2017-12-11 14:40 ` Gerd Stolpmann
2017-12-11 16:10 ` Ian Zimmerman
2017-12-11 16:47 ` Viet Le
2017-12-11 17:10 ` Yotam Barnoy
2017-12-11 18:56 ` Robert Muller
2017-12-11 19:23 ` Yawar Amin
2017-12-11 21:10 ` Marshall
2017-12-11 17:29 ` Yawar Amin
2017-12-11 17:59 ` Ian Zimmerman
2017-12-11 18:30 ` Gerd Stolpmann
2017-12-13 8:22 ` Sebastien Ferre
2017-12-13 9:26 ` Evgeny Khramtsov
2017-12-13 10:37 ` David Allsopp
2017-12-13 16:38 ` Marshall
2017-12-13 16:44 ` Yawar Amin [this message]
2017-12-13 17:20 ` David Allsopp
2017-12-13 17:51 ` Yawar Amin
2017-12-13 17:39 ` Hendrik Boom
2017-12-13 17:55 ` Robert Muller
2017-12-13 18:19 ` Viet Le
2017-12-13 19:29 ` Yawar Amin
2017-12-13 8:55 ` Nicolas Boulay
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='CAJbYVJKE7tf_GNKLFR=xF8V7nGcVh3s1yAtnmO_OOi8W90fOZw@mail.gmail.com' \
--to=yawar.amin@gmail.com \
--cc=caml-list@inria.fr \
--cc=marshall@logical.net \
/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).