Fix future object safety of BufferAccess #966
Merged
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.
It was recently discovered in rust-lang/rust#50781 that
Self: Trait
bounds in trait methods are not really object-safe. This will be made into a warning by rust-lang/rust#50966, and vulkano will be affected by the warning.There is no actual unsafety in the affected code in vulkano, making this unsafe would require some weird impls in vulkano itself.
The fix looks simple, to move
fn len
fromBufferAccess
to being directly inTypedBufferAccess
.