-
Notifications
You must be signed in to change notification settings - Fork 30
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
coqdoc / website #92
Comments
the order of files in _CoqProject has no influence on anything I know except on the coqdoc (I thought it does someting with compilation order, but that is not the case appearently). So reordering everything would be possible. |
@mrhaandi @DmxLarchey would you be fine with such a change? Lots of files would have to be touched, so I'm not I can finish it today, but if it's possible it would be neat to ship the library with clean coqdoc. |
I support it. Useful documentation is worth the effort. |
Well of course I do support the effort as well but I do not think there is a need to rush to ship it with the release. |
Currently, our coqdoc is a complete mess.
I don't know how to fix this in a good way, and it's well possible that we want to ignore the issue for now.
Alternatively, we can in a first step remove all coqdoc headings generation by replacing
(**
with(*
everywhere in the code. In a second step, we can then add coqdoc headings in theProblem.v
andProblem_undec.v
files only. That way, the coqdoctoc.html
file gives a good overview over the library.Downside: For this to work well, we would have to move the
Problem.v
andProblem_undec.v
lines in_CoqProject
to be in the right order.The text was updated successfully, but these errors were encountered: