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
Currently primitive types have encodings that do not allocate (they're defined from static strings) but compositions like structs either have to jump through hoops and use different encoding strings for different architectures or accept the cost of allocating a string and pushing the encoding of their fields.
Is there a better way to do this, where encodings from structs could more simply be composed without allocating?
The text was updated successfully, but these errors were encountered:
Currently primitive types have encodings that do not allocate (they're defined from static strings) but compositions like structs either have to jump through hoops and use different encoding strings for different architectures or accept the cost of allocating a string and pushing the encoding of their fields.
Is there a better way to do this, where encodings from structs could more simply be composed without allocating?
The text was updated successfully, but these errors were encountered: