-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coqdep spuriously warns about multiple files with the same name #11631
Comments
Indeed this is a bug; we hope to address that once we do the loadpath cleanup after the Dune switch. On the other hand |
Indeed, the logic looks wrong. I don't remember this code very well though, I wouldn't mind somebody else writing the fix though :/ |
FWIW I get the same warnings while using |
As explained in #12251 but not here,
|
Add `ds_` prefix to each name. Bug reports: coq/coq#11631 ocaml/dune#3389
Add `ds_` prefix to each name. Bug reports: coq/coq#11631 ocaml/dune#3389
- It stops relaying on the order of hash table keys to find an appropriate From path, building instead a direct map of each "From dirpath Require dirpath'" to a full physical path. - Incidentally, it takes From into account to warn about clashes - This fixes coq#11631 (initial report) - This fixes coq#14539
- It stops relaying on the order of hash table keys to find an appropriate From path, building instead a direct map of each "From dirpath Require dirpath'" to a full physical path. - Incidentally, it takes From into account to warn about clashes - This fixes coq#11631 (initial report) - This fixes coq#14539
- It stops relaying on the order of hash table keys to find an appropriate From path, building instead a direct map of each "From dirpath Require dirpath'" to a full physical path. - Incidentally, it takes From into account to warn about clashes - This fixes coq#11631 (initial report) - This fixes coq#14539
- It stops relaying on the order of hash table keys to find an appropriate From path, building instead a direct map of each "From dirpath Require dirpath'" to a full physical path. - Incidentally, it takes From into account to warn about clashes - This fixes coq#11631 (initial report) - This fixes coq#14539
- It stops relaying on the order of hash table keys to find an appropriate From path, building instead a direct map of each "From dirpath Require dirpath'" to a full physical path. - Incidentally, it takes From into account to warn about clashes - This fixes coq#11631 (initial report) - This fixes coq#14539
- It stops relaying on the order of hash table keys to find an appropriate From path, building instead a direct map of each "From dirpath Require dirpath'" to a full physical path. - Incidentally, it takes From into account to warn about clashes - This fixes coq#11631 (initial report) - This fixes coq#14539
…4539. Co-authored-by: Ali Caglayan <alizter@gmail.com> Co-authored-by: Gaëtan Gilbert <gaetan.gilbert@skyskimmer.net>
- It stops relaying on the order of hash table keys to find an appropriate From path, building instead a direct map of each "From dirpath Require dirpath'" to a full physical path. - Incidentally, it takes From into account to warn about clashes - This fixes coq#11631 (initial report) - This fixes coq#14539
…4539. Co-authored-by: Ali Caglayan <alizter@gmail.com> Co-authored-by: Gaëtan Gilbert <gaetan.gilbert@skyskimmer.net>
Description of the problem
Given a
B.v
withFrom dir.a Require Import A.
, and the directory structure:Running
coqdep -R . dir B.v
prints:So it seems to choose the correct
A.v
despite the warning. The warning goes away if the line is changed toRequire Import dir.a.A.
or if-Q
is used instead of-R
.Coq Version
master and at least back to 8.10.
The text was updated successfully, but these errors were encountered: