core: Relax lifetime constraint on msgs
in I2CTransfer::transfer()
#89
+4
−4
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 change enables users of
i2cdev
to create generic functions onT: I2CTransfer
that have output buffers constructed separately from theI2CMessage
array, like the following:Before this,
messages
would not satisfy the constraints of.transfer()
, becausemessages
does not live as long as one of the output buffersout
:The error message is a little confusing, but basically
&'a mut [Self::Message]
is forcing the array ofI2CMessage
s to match the lifetime of the buffers in the messages, which is not strictly necessary: the array of messages can have a different lifetime than the buffers. After this change, the above example compiles successfully.