Closed Skirmisher closed 3 years ago
Hi, thanks for the issue report. This should be resolved via https://github.com/Robbepop/modular-bitfield/issues/56. So maybe we can close this issue in favor of the other more detailed one. What do you think?
Anyhow, thanks for the nice crate!
Glad to know! :)
Oops! I searched for some of the warning text and not just "warning" so I didn't see it, sorry.
I've noticed that generated functions on a
#[bitfield]
struct will cause warnings when not used, such as this:In this case I have no need to create an empty bitfield (despite the
Default
trait), nor forinto_bytes
, but there doesn't seem to be a way to silence these warnings or disable these functions. If there's no way to prevent the warnings, perhaps makingskip
available at the top level (or adding a similar attribute) would be appropriate?For reference, the struct I'm using is below, based off the
binread
bitfield example:Anyhow, thanks for the nice crate! Its usage in my project is minor, but appreciated nonetheless :)