From: Florian Angeletti <florian.angeletti@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] module dependency question
Date: Thu, 16 Jul 2026 15:34:41 +0200 [thread overview]
Message-ID: <ed3b12f5-64e4-496a-a763-a58d0ebd2a80@inria.fr> (raw)
In-Reply-To: <CACTzTFBk=sFr=6ant66Hm9FAQ26hf+PauMY7R7wR6hspBd=8Pg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
What is the motivation for adding the constraint of not opening any
other files?
You will need to open the interface of M to discover its dependencies at
one point or another.
On 16/07/2026 at 17:19, K wrote :
> Is iterating over the typexpr the right or reasonable way of
> uncovering that transitive dependency (on type N.t specifically rather
> than on the module N in its entirety) without recourse to opening any
> other file?
>
> On Thu, 16 Jul 2026 at 13:07, Florian Angeletti <octa@polychoron.fr>
> wrote:
>
> In your example, `N` will be a dependency of `M` and thus a
> transitive
> dependency of the current module.
>
[-- Attachment #2: Type: text/html, Size: 1546 bytes --]
prev parent reply other threads:[~2026-07-16 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 14:53 K
2026-07-16 13:07 ` Florian Angeletti
2026-07-16 15:19 ` K
2026-07-16 13:34 ` Florian Angeletti [this message]
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=ed3b12f5-64e4-496a-a763-a58d0ebd2a80@inria.fr \
--to=florian.angeletti@inria.fr \
--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