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
Instead, if there is no way to compute malloc_size_of, we should either make it a compile-time/link-time error, or change the API to return an Option<usize> instead of usize (although, this may be a substantial rewrite).
I don't have time to work on this today, but feel free to ask me any questions.
As mentioned in paritytech/substrate#6745, this is not future-proof and leads to runtime panics.
Instead, if there is no way to compute
malloc_size_of
, we should either make it a compile-time/link-time error, or change the API to return anOption<usize>
instead ofusize
(although, this may be a substantial rewrite).I don't have time to work on this today, but feel free to ask me any questions.
cc @expenses , @cheme
The text was updated successfully, but these errors were encountered: