Skip to Content.
Sympa Menu

coq-club - Re: [Coq-Club] option to disable partially qualified Require Imports

coq-club AT inria.fr

Subject: The Coq mailing list

List archive

Re: [Coq-Club] option to disable partially qualified Require Imports


Chronological Thread 
  • From: Guillaume Melquiond <guillaume.melquiond AT inria.fr>
  • To: coq-club AT inria.fr
  • Subject: Re: [Coq-Club] option to disable partially qualified Require Imports
  • Date: Fri, 18 Sep 2020 15:45:16 +0200

Le 18/09/2020 à 15:28, Ralf Jung a écrit :

>> Another possibility would be to relax some requirements of From-Require.
>> Currently, "From A.B.C Require D.E.F" means that not only the path
>> should start with A.B.C and finish with D.E.F, but also that there
>> should be no overlap between A.B.C and D.E.F. If the second constraint
>> was removed, then Require would become non-ambiguous for people who have
>> to use messy libraries.
>
> I don't see how accepting even more paths for a given import can possibly
> resolve any ambiguities? "From A.B.C Require A.B.C" would then match both
> "A.B.C" and "A.B.C.*.A.B.C".

Because I am assuming the library's author is not dumb enough to have a
hierarchy A/B/C/**/A/B/C.v.

At some point, we have to accept that we cannot always win against dumb
or malicious users. They will always find a way to circumvent the system.

I don't even understand why we are wasting so much on this issue when it
is still possible to write the following in Coq:

Cd "/tmp".
Extraction passwd.

Best regards,

Guillaume



Archive powered by MHonArc 2.6.19+.

Top of Page