Fix incorrect platform-specific Verifier documentation #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the incorrect documentation on docs.rs pointed out in #56. The root cause of the problem was that when I originally wrote the Android documentation parts, I used the
doc_auto_cfg
feature instead of thedoc_cfg
by mistake. The former is too eager and assumes that anything with a#[cfg()]
gate is only available under the gated conditions.Instead of trying to get what we want with
doc_auto_cfg
, and especially since we only have one item that needs special documentation treatment, I've instead switched to usedoc_cfg
"manually". This approach was partially inspired by how Tokio generates their platform-specific documentation.Documentation generated from a Windows system:
Documentation generated on a macOS system:
Finally, I fixed a broken doc warning in the README when referencing the
new_with_extra_roots
function. Since this function only exists on Linux right now, documentation built on Windows and macOS won't make that symbol available. I've chosen to link to docs.rs instead for that function at least until the other platforms gain that function too.Closes #56