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
When using this crate I noticed that the BufMut::put method requires Self to be Sized.
This makes it difficult for me to use that function in ?Sized contexts for better optimizations. Is there a reason
this trait bound is necessary?
I looked at BufMut::put and BufMut::put_slice and it seems that neither method uses functions that require Self: Sized while put does require Sized and put_slice does not. Could the trait bound be removed from the api?
The text was updated successfully, but these errors were encountered:
GrizzlT
changed the title
Unnecessary Sized constraint on BufMut::
Unnecessary Sized constraint on BufMut::put method
May 8, 2023
GrizzlT
changed the title
Unnecessary Sized constraint on BufMut::put method
Unnecessary Sized constraint on BufMut::put method?
May 8, 2023
When using this crate I noticed that the
BufMut::put
method requiresSelf
to beSized
.This makes it difficult for me to use that function in
?Sized
contexts for better optimizations. Is there a reasonthis trait bound is necessary?
I looked at
BufMut::put
andBufMut::put_slice
and it seems that neither method uses functions that requireSelf: Sized
whileput
does requireSized
andput_slice
does not. Could the trait bound be removed from the api?The text was updated successfully, but these errors were encountered: