-
Notifications
You must be signed in to change notification settings - Fork 37
Please include Async documentation on docs.rs #52
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
Comments
Someone asked about this on SO: |
@tal-zvon Not great, but you might be able to use something like |
Yup - that's one way to go. Would be nice if we didn't need to jump through hoops to see that section of documentation though. |
Hey there, thanks for opening the issue. It's possible to use docsrs attributes ( hopefully once we ship |
Awesome! I'd close the issue, but it seems that it's set to auto-close when 0.4.1 is released. I guess I'll keep it open for people who run into the same issue, so they can find the answer easier, until the 0.4.1 is released, which will both solve, and auto-close this. Thanks |
There is no mention of
AsyncLineEventHandle
anywhere on docs.rs. The only way to see this documentation is to build it locally withcargo doc
, which is a bit of a pain, especially since many of the people usinggpio-cdev
are working on a raspberry pi, and if they are running the lite version of Raspbian, without a GUI, as I am, there is no browser, socargo doc --open
won't work. We need to manually go in and copy the docs directory to a different computer to read it.When I did
cargo doc
on my project, it generated 16k files. Using scp to copy them over to my other computer was going to take like half an hour. I had to interrupt the scp copy operation, tar the 16k of doc html files, transfer it as one file, and unarchive it before opening it. The whole process took like 20 minutes. It would have been nice if I could have just found the documentation on docs.rs in seconds, as I do with most other documentation.The text was updated successfully, but these errors were encountered: