-
Notifications
You must be signed in to change notification settings - Fork 786
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
Can documentation be clearer, please? #831
Comments
See https://github.com/Cyan4973/xxHash/blob/dev/LICENSE#L1C1-L3
See https://github.com/Cyan4973/xxHash/tree/dev/doc
See https://github.com/Cyan4973/xxHash/blob/dev/Doxyfile For example, git clone https://github.com/Cyan4973/xxHash.git
cd xxHash
doxygen
open doxygen/html/index.html Actually, we should maintain it though. |
@Cyan4973, to maintain the document, should we include So far, I've got the following warnings from
|
@t-mat I appreciate your response, thank you. This isn't the first time I couldn't navigate myself on GitHub over something so trivial (I don't know how I fail so miserably), but just in case I am not the only one who is defective, do you think it is a good idea to put these references (at least for specification) on the main page README.md? |
Yes, this is a worthwhile goal |
I could fix the first 2 minor |
I'll find a way to resolve this issue. |
@t-mat improvements to the I presume one possible follow up could be to generate a version after the release, and reference it from the xxhash homepage ? |
Yes, it's nice to have Google-able document! I'd also like to recommend to include version in the URL of the document. For example, CMake's document URL contains version : https://cmake.org/cmake/help/v2.8.12/cmake.html |
Doxygen documentation has been added to homepage : |
This technically barely falls under "issues", but I am having an issue trying to figure out who the actual designer of this algorithm is and trying to find the specifications of it in case I want to implement the algorithm myself. Also, the list of functions and how they are used is hard to find too (I didn't find it). So, please, will someone be kind to make it all more accessible?
The text was updated successfully, but these errors were encountered: