-
Notifications
You must be signed in to change notification settings - Fork 36
Rocq Object Metadata #80
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
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Jim Fehrle <[email protected]>
|
I am in favor of this concept; subscribing. Small comments on the sketched details For docstrings, comments right before the definition are somewhat of a cross-language standard at this point. We should consider adopting it. Perhaps alias could be called "suggest"? I think the idea of adding additional searches in response to which a definition should be shown is desirable, but I am less sure about convertibility as a central concept there. Sometimes a non-convertible definition is a good search result anyway, and at other times a convertible definition is not applicable because heuristic conversion takes too long. Instead I'd trust the metadata author to choose what searches the definition should be shown for without relating that choice to convertibility. I'd also be interested in having |
|
Have you considered the lean search tools? It would be nice to have something along these lines for Rocq. |
I agree with you, we should opt for that.
Yes, I agree. Or maybe "similar" or "related"... or something drawn from ontology concepts?
What do you mean "for example warnings" ? |
Yes of course, I know several people working in this direction, and it is definitely connected to this rfcs since it should provide all the meta-data required by the potential applications. |
|
I did not know about leanexplore, thanks for mentioning it |
No description provided.