examples/rust: Update CoAP example modules#20821
Merged
maribu merged 1 commit intoRIOT-OS:masterfrom Aug 19, 2024
Merged
Conversation
This updates the use of two deprecated items.
maribu
approved these changes
Aug 19, 2024
maribu
added
the
CI: ready for build
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Contribution description
This updates the use of two deprecated items to the latest idioms in riot-wrappers 0.8.
Testing procedure
Green CI should suffice.
Issues/PRs references
This unblocks testing of RIOT-OS/rust-riot-wrappers#90: riot-wrappers 0.9 is developed and tested as 0.8.999, because its claim is that if all deprecation warnings of latest 0.8 are resolved, and you don't do something weird1, all can still run.
Footnotes
Such as assigning the error from a known can-not-err result to a
!type rather than toInfallible– that is a breaking API change, but practical breakage is not expected, and at worst fixed by implementing some conversion to do the same when going from!as forInfallible. ↩