-
Notifications
You must be signed in to change notification settings - Fork 2.1k
nanocoap: use void * for payload bytes #17990
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
Conversation
Urgh, so while this is a non-breaking change for C code, it breaks the Rust wrappers - how can this be resolved @chrysn |
Updating to riot-sys 0.7.7 enables support for more recent C2Rust versions, and to riot-wrappers 0.7.22 unblocks [17990]. [17990]: RIOT-OS#17990
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK. This is a very sensible API change that should go unnoticed for the C callers and the Rust wrappers have apparently been updated.
Looks like the automerge was faster than giving the CI another spin :) Anyway, the next CI run with also test this. |
Updating to riot-sys 0.7.7 enables support for more recent C2Rust versions, and to riot-wrappers 0.7.22 unblocks [17990]. [17990]: RIOT-OS#17990 (cherry picked from commit ec498cd)
Contribution description
Casting payload to
(uint8_t *)
or(void *)
is really annoying and unnecessary.Testing procedure
No change in code output or on the caller side, just more convenient interface.
Issues/PRs references