-
Notifications
You must be signed in to change notification settings - Fork 53
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
Feature request: Remove dependence of elpi on stdlib #677
Comments
FTR we used coq-elpi in Trocq which was based on HoTT and for which we plan to keep a HoTT option... I cannot remember a dependency on the prelude, where is it? |
Yeah, I'm not exactly sure. All I know is that when I do
|
I think I used poor terminology. It "loads" the libraries, but does not import them. Still, due to an unrelated bug with typeclass databases (coq/coq#16934) as long as loading Elpi causes the prelude to be loaded, it will cause headaches trying to use Elpi in this setting. |
I have investigated this issue and I think that this step in the build script is part of it. Line 12 in 2ef66b2
The
The fact that the |
Those plugins are from the prelude, they are loaded by String because it doesn't use -noinit. |
That is a hack waiting for ocaml/dune#9591 to be merged. Please ping the dune devs. |
It would broaden the applicability of elpi if it could be used in projects compiled with the --no-init flag. I am interested in using Elpi in the Coq-HoTT library which does not use Prop anywhere and redefines equality to live in Type. Importing the stdlib is not itself fatal but one has to then be careful to avoid using any terms which are defined in the standard library.
Furthermore, if we import the stdlib it must be imported everywhere, which is annoying. It is currently not realistic/practical to import the stdlib only in the files that directly use Elpi due to a bug in the hint database system.
The text was updated successfully, but these errors were encountered: