Skip to content
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

Have a dedicated import category for HB #429

Open
CohenCyril opened this issue Jun 27, 2024 · 3 comments
Open

Have a dedicated import category for HB #429

CohenCyril opened this issue Jun 27, 2024 · 3 comments

Comments

@CohenCyril
Copy link
Member

When importing, we should be able to be selective about what should or should not be imported from a module/file containing HB declarations, honoring the import category directive of Coq.

Spotted by @ggonthier

@gares
Copy link
Member

gares commented Jun 27, 2024

HB declares Coq standard objects, like CS instances, and Elpi objects (cluases).

Do you want a sort of meta-category encompassing all of these, or be able to give a category name to the Elpi objects?

The former needs to change Coq, the latter Elpi.

@CohenCyril
Copy link
Member Author

I think we need both eventually.

@CohenCyril
Copy link
Member Author

But the latter would already be very useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants