-
Notifications
You must be signed in to change notification settings - Fork 42
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
Linkify builtin types like Sort
, Prop
, and Pi
#90
Comments
In general it is unclear right now what thing we want to use for documentation that is not directly related to code. Despite building doc-gen4 I have in fact basically no clue about web development at all :D so implementing this type of prose documentation is something I don't want to invest too much time on when I can instead be helping at the code generator front. There have also been a few people that want to integrate existing documentation tools better with the Lean stuff like LeanInk so maybe this would be the place for documentation like this to live? I'm unsure, where to put what documentation is still an open question :/ |
The prose itself isn't really what matters here; it's primarily about being able to ask "what instances does mathlib put on pi types", which is very much directly related to code. The components of doing so are roughly:
|
I do have an implementation in #93 for sort variants. I am not yet sure how to do pi types in the current framework. It might be that this requires a patch similar to the one we had for function applications with constants in the compiler. |
It would be good to forward-port the features from:
Pi
/Sort
/Type
/Prop
leanprover-community/doc-gen#172Instance lists for builtin types, like we already have for inductive types
Distinguishing between different ways of printing pi types. This probably should adapt to the Lean4 changes around pretty-printing.
Linkifying these special types
The PRs above are all centered around this page: https://leanprover-community.github.io/mathlib_docs/foundational_types.html
The text was updated successfully, but these errors were encountered: