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
Upon further reflection, all those datatypes can use custom implementations anyway, so it's possible no design choices are needed (all of them are even bytes so writeByte can be used for all of them. That's at most 8 calls.)
Running the assertions multiple times is still a concern though; it might be an acceptable loss though, given they'll all just be using writeByte.
UInt64 and Int64 are rejected at this moment -- the name is deceiving and creates the illusion of 64-bit integers. If 64-bit read/write functions are necessary, they can be added manually.
Should include things like Int32 and UInt32. Should also shorthand some like writeByte -> writeUInt8.
Unclear how to handle assertions and testing. Seems like it may add a lot of overhead to run assertions twice in cases like
writeFloat32
.The text was updated successfully, but these errors were encountered: