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
Is there a discussion somewhere about why X_excess isn't just called X; i.e., all of the "default" functions return the actual allocation size which can be used or ignored? Are there allocators which have different behavior when _excess is called (and should that behavior be supported)?
Returning
Excess
when allocating is useful for collections like (Raw
)Vec
. Currently, only these methods are provided:alloc_excess
realloc_excess
In order to make those collection work with the excess api, these methods have to be added:
alloc_zeroed_excess
grow_in_place_excess
shrink_in_place_excess
The text was updated successfully, but these errors were encountered: