You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if a PR to change the u32 slice in the transmit_preserve callback to a u8 would be acceptable? i.e. PTX: FnMut(Mailbox, TxFrameHeader, &[u32]) -> P, to PTX: FnMut(Mailbox, TxFrameHeader, &[u8]) -> P,
It would be a breaking change, but it would bring the API in line with the other data parameters which are all &[u8]s.
The text was updated successfully, but these errors were encountered:
projectgus
changed the title
transmit_preserve pending argument as u8 slice?
transmit_preserve pending data parameter as u8 slice?
Sep 6, 2024
(Sorry for the sudden flurry of posts)
I was wondering if a PR to change the u32 slice in the
transmit_preserve
callback to au8
would be acceptable? i.e.PTX: FnMut(Mailbox, TxFrameHeader, &[u32]) -> P,
toPTX: FnMut(Mailbox, TxFrameHeader, &[u8]) -> P,
It would be a breaking change, but it would bring the API in line with the other
data
parameters which are all&[u8]
s.The text was updated successfully, but these errors were encountered: