?Sized bounds for rc::Weak::as_ptr and friends #74022
Closed
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.
Specifically, this relaxes the bounds on
rc::Weak::as_ptr
,into_raw
, andfrom_raw
fromimpl<T> Weak<T>
toimpl<T: ?Sized> Weak<T>
.This is a follow-up to #73845, which did the impl work required to be able to relax these bounds.
IIUC, this technically stabilizes that "something like
size_of_val_raw
" is possible to do. However, I believe the part of the functionality required by these methods here -- specifically, getting the size of a pointee from a pointer where it may be dangling iff the pointee isSized
-- is uncontroversial enough to stabilize these methods without a way to implement them on stable Rust.ATTN: This changes (relaxes) the (input) generic bounds on stable
fn
!