From: Leo White <leo@lpw25.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Are implicit modules too implicit?
Date: Wed, 02 Mar 2016 08:37:16 -0500 [thread overview]
Message-ID: <1456925836.1464341.537330890.53BDFE3A@webmail.messagingengine.com> (raw)
In-Reply-To: <867fhlgjmj.fsf@gmail.com>
> To me, this means going from a call-site, to the actual
> implementation is very difficult especially since I cannot even do some
> sort of grep to find all those things that implement an implicit module
> type.
The best way of finding a variable's definition is to use merlin to jump to definition.
The same will be true for implicit call sites.
Depending on how libraries are designed I would not expect it to be difficult to locate
the instances by hand. They are managed with the same scoping mechanisms as
ordinary values, and since they should rarely be used by name they can also be
given nice descriptive searchable names.
Regards,
Leo
next prev parent reply other threads:[~2016-03-02 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 12:16 Malcolm Matalka
2016-03-02 13:37 ` Leo White [this message]
2016-03-02 13:59 ` Malcolm Matalka
2016-03-02 14:17 ` Yaron Minsky
2016-03-02 14:24 ` Leo White
2016-03-02 15:57 ` Malcolm Matalka
2016-03-02 18:59 ` Gabriel Scherer
2016-03-02 14:30 ` Gerd Stolpmann
2016-03-02 15:09 ` Leo White
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=1456925836.1464341.537330890.53BDFE3A@webmail.messagingengine.com \
--to=leo@lpw25.net \
--cc=caml-list@inria.fr \
/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).