-
Notifications
You must be signed in to change notification settings - Fork 66
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
Rustdocs Usage #26
Comments
Thanks =) I will try this out soon |
Let me play around in your fork. It's an interesting idea |
https://github.com/hemangandhi/functional-programming-jargon.rs/blob/doctest/DOCTEST_TODO.md ^ this is my vision so far, though I definitely don't expect the last goal to happen/get merged in any time soon. |
@hemangandhi Great ideas! I love it. I can work on the linting issues tonight. I was actually checking out how to enable RustDoc the other day according to your example folk but I got confused ... ;)... Also, if you are interested in turning this into an actual module, let's do this in a separate project. Come and join us on telegram =) https://t.me/joinchat/Hj2nWg58UEWmMFprHvs-iQ |
We have half solved this issue because now we have a documentation automatically generated on crates.io |
I was wondering if rustdoc was useful for this project (more or less fiddling to get maximal mileage out of rust's tooling).
Particularly, I have a small experiment in a fork.
I was wondering if getting the rest of the README into such a format would be reasonable. I think there are a few advantages:
#[test]
keeps the source in one place and automatically ensures consistency.target/docs
).This seems to have a few drawbacks:
///
with md formatting) might make linting and editing harder.If this is interesting, I've also experimented on the azure pipeline, so was wondering how to test that?
The text was updated successfully, but these errors were encountered: