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
{{ message }}
This repository has been archived by the owner on Sep 25, 2018. It is now read-only.
For example the lowering an attribute message takes a 32bit int, the raising a 16bit int for the attribute id.
I think we could maybe do a sendId() function which always sends with either 16 or 32bit and make sure that one is always used. (Maybe it would make sense to introduce a type wrapper for ids so they cannot be mixed with integers anywhere (then we also kill all this unsigned <-> signed randomness)
The text was updated successfully, but these errors were encountered:
For example the lowering an attribute message takes a 32bit int, the raising a 16bit int for the attribute id.
I think we could maybe do a
sendId()
function which always sends with either 16 or 32bit and make sure that one is always used. (Maybe it would make sense to introduce a type wrapper for ids so they cannot be mixed with integers anywhere (then we also kill all this unsigned <-> signed randomness)The text was updated successfully, but these errors were encountered: