We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Cargo doc currently emits tons of warnings when run on this codebase.
cargo clean --doc && cargo doc
... warning: could not parse code block as Rust code --> src/toxencryptsave/mod.rs:189:5 | 189 | / Decrypts provided `data` with `self` `PassKey`. 190 | | 191 | | Decrypted data is smaller by [`EXTRA_LENGTH`](./constant.EXTRA_LENGTH.html) 192 | | than encrypted data. ... | 212 | | assert_eq!(passkey.decrypt(&[]), Err(DecryptionError::Null)); 213 | | ``` | |_______^ | = note: error from rustc: unknown start of token: `
A bit of background. Markdown supports two modes for code blocks. The more common mode uses tick marks like so:
``` // code block.. ```
but there is another mode that uses indentation:
// code block..
The issue likely has to do with rustdoc not stripping whitespace from multiline doc comments in its unindent-comments pass.
The text was updated successfully, but these errors were encountered:
I have development profficiency and I’m a naitive english speaker so I can proofread documentation if requested.
Yes, this would be very helpful.
Sorry, something went wrong.
No branches or pull requests
Cargo doc currently emits tons of warnings when run on this codebase.
cargo clean --doc && cargo doc
A bit of background. Markdown supports two modes for code blocks. The more common mode uses tick marks like so:
but there is another mode that uses indentation:
The issue likely has to do with rustdoc not stripping whitespace from multiline doc comments in its unindent-comments pass.
The text was updated successfully, but these errors were encountered: