From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Yawar Amin <yawar.amin@gmail.com>
Cc: "SF Markus Elfring" <elfring@users.sourceforge.net>,
"Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>,
"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] Checking support for string concatenation by OCaml
Date: Tue, 21 Nov 2017 18:42:41 +0100 [thread overview]
Message-ID: <CAPFanBGxV7RPd1OwLa-ZsEap7YzqxPTYaSc1=F8-i-ezOgawfA@mail.gmail.com> (raw)
In-Reply-To: <CAJbYVJLWMTbnNfyAyJmW1sknAeAqgrnY1Y4P9QoXdN0xvQGudA@mail.gmail.com>
This would create a cyclic dependency as String depends on Pervasives
(for (+), for example).
On Tue, Nov 21, 2017 at 5:45 PM, Yawar Amin <yawar.amin@gmail.com> wrote:
> Now that you mention it, `(^)` should really be defined in the `String`
> module and then aliased from `Pervasives`. This seems like a reasonable PR
> to send to the OCaml repo.
>
> On Tue, Nov 21, 2017 at 11:28 AM, SF Markus Elfring
> <elfring@users.sourceforge.net> wrote:
>>
>> > It is documented in stdlib reference:
>> >
>> > https://caml.inria.fr/pub/docs/manual-ocaml/libref/Pervasives.html
>>
>> Thanks for your link.
>>
>> Would it be nice to repeat such information also at other places
>> in the provided documentation?
>>
>> Are you interested to compare the run time characteristics from the usage
>> of the operator “^” (for string concatenation) to the other available
>> programming interfaces?
>>
>> Regards,
>> Markus
>>
>> --
>> 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
>
>
next prev parent reply other threads:[~2017-11-21 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 16:10 SF Markus Elfring
2017-11-21 16:15 ` Nicolás Ojeda Bär
2017-11-21 16:28 ` SF Markus Elfring
2017-11-21 16:45 ` Yawar Amin
2017-11-21 17:42 ` Gabriel Scherer [this message]
2017-11-21 19:22 ` Rodolphe Lepigre
2017-11-22 10:18 ` David Allsopp
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='CAPFanBGxV7RPd1OwLa-ZsEap7YzqxPTYaSc1=F8-i-ezOgawfA@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=elfring@users.sourceforge.net \
--cc=nicolas.ojeda.bar@lexifi.com \
--cc=yawar.amin@gmail.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).