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
I'm just not sure which. Things I need to think through:
If I use primitives, I'll need to add something to the effect of Float64Ptr and CoerceInt64Ptr to the types in the dynamic package. Should I be concerned about the usability of this for the dynamic package? It wont be a pointer to the actual value.
If I use dynamic, that'll be a lot cleaner but I won't be able to cleanly coerce. This is a problem as some accessors currently coerce int values.
Doing so should improve performance of enc/dec.
The text was updated successfully, but these errors were encountered:
In an effort to move things along, I used
interface{}
for dynamic fields on the internal types used for (un)marshaling.These need to be migrated to either primitive pointer types or dynamic types:
I'm just not sure which. Things I need to think through:
Float64Ptr
andCoerceInt64Ptr
to the types in the dynamic package. Should I be concerned about the usability of this for the dynamic package? It wont be a pointer to the actual value.Doing so should improve performance of enc/dec.
The text was updated successfully, but these errors were encountered: