doc: Various fixes from cargo doc warnings
#125
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
One nontrivial change included in here is the genericity over WritePhydatPointer (the mutability of the phydat in writes), which was internal and only necessary tue to a chnage from way longer ago than RIOT versions are still supported.
chrysn
added a commit
that referenced
this pull request
Sep 16, 2024
The fixes in [125] made the warnigns go away, but [`.foo()`] does not fix the warnings, it just looks so wrong that rustdoc doesn't even warn any more. [125]: #125
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
One nontrivial change included in here is the genericity over WritePhydatPointer (the mutability of the phydat in writes), which was internal and only necessary tue to a chnage from way longer ago than RIOT versions are still supported.