Closed daboross closed 4 years ago
I'd rather not expose HexSlice
, so adding a constructor sounds good. Ideally the user wouldn't even have to deal with raw Attribute
s (instead only with Characteristics and Services), but we aren't there yet.
Sounds good to me! Submitted #139. And again, my apologies for communicating in short bursts with periods of radio silence.
Hi!
It looks like
rubble::att::Attribute
, https://jonas-schievink.github.io/rubble/rubble/att/struct.Attribute.html, has the value data wrapped in arubble::utils::HexSlice
. But as the docs indicate,HexSlice
isn't public -utils
isn't public, andHexSlice
isn't re-exported. Thus, as far as I can tell, it isn't possible to construct anAttribute
from outside the crate?If this is a problem, do you it'd be reasonable to just re-export
HexSlice
from the crate root, or would it be better to add a constructor and accessors toAttribute
which allow interacting with value as an&[u8]
?