From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Leo White <leo@lpw25.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Are implicit modules too implicit?
Date: Wed, 02 Mar 2016 15:30:13 +0100 [thread overview]
Message-ID: <1456929013.13827.52.camel@e130.lan.sumadev.de> (raw)
In-Reply-To: <1456925836.1464341.537330890.53BDFE3A@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
Currently I'm in a Scala project where there are a number of implicits,
and the question which implicit is actually used is a real one. Having
support in Merlin is good, but I think there could also be support in
the compiler. What about adding a warning "implicit X is resolved
as ..." which can be used for tracing the resolution during the build?
Gerd
Am Mittwoch, den 02.03.2016, 08:37 -0500 schrieb Leo White:
> > 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
>
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-02 14:30 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
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 [this message]
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=1456929013.13827.52.camel@e130.lan.sumadev.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=leo@lpw25.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