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
In type-coercions.md, the following is really not clear:
* TyCtor(`T`) to TyCtor(`U`), where TyCtor(`T`) is one of
- `&T`
- `&mut T`
- `*const T`
- `*mut T`
- `Box<T>`
and where `U` can be obtained from `T` by [unsized coercion](#unsized-coercions).
<!--In the future, coerce_inner will be recursively extended to tuples and
structs. In addition, coercions from subtraits to supertraits will be
added. See [RFC 401] for more details.-->
Ideally, the text should not require deciphering. It seems to be redundantly stating that &T can be coerced to &U. However, is it merely stating that &, &mut, *const, *mut, and Box have special permissibility when unsized coercions exists for their argument types.
The text was updated successfully, but these errors were encountered:
I feel like this whole bullet point might have simply become seriously outdated, because it appears to describe some (but not all) of the coercions that now work via CoerceUnsized. Here’s some relevant forum discussion.
In
type-coercions.md
, the following is really not clear:Ideally, the text should not require deciphering. It seems to be redundantly stating that
&T
can be coerced to&U
. However, is it merely stating that&
,&mut
,*const
,*mut
, andBox
have special permissibility when unsized coercions exists for their argument types.The text was updated successfully, but these errors were encountered: