[DO NOT MERGE] Allow a type implementing phy::Device
to contain borrowed data
#697
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.
Previously, a limitation of Rust's type system required a device to
implement
phy::Device<'a>
for all lifetimes, including'static
, tobe able to call methods on
iface::Interface
. This prevented typesimplementing
phy::Device<'a>
from containing any borrowed data.Now that Rust supports GATs (generic associated types), it is possible
to lift this restriction and allow implementations of
phy::Device<'a>
which contain borrowed data.