Loïc Damien

The `BitRange` trait was never really intended to be used as-is. The goal of this trait is the method can be called from the code generated by the macro, not...

> So I'm using bitfield wrong / not as intended? The intended use of this crates is really to use the `bitfield!` macro with defined fields, and then you access...

My reasoning was that bitfield is only a thin wrapper around the inner type and as such you will likely want to have access to the inner type. But it...

You can already add a `pub` modifier to a field. This will make the two method public. There is an example in the `bitfield_fields` documentation. The goal of this issue...

This is documented with the phrase "The syntax of this macro is the syntax of a tuple struct, including attributes and documentation comments, " on https://docs.rs/bitfield/0.13.0/bitfield/macro.bitfield.html for the struct and...

Thanks for the suggestion, I will try to add something. If you want to see the resulting code to evaluate it, you can use [`cargo expand`](https://github.com/dtolnay/cargo-expand) on a small project...

I recently stated using `testQuick` with sbt. For me, it seems to works correctly. This is really a time saver. It would be really nice to have that supported in...

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option

> I'm not sure the library should make this decision. But the library already make a decision: stuffing the messge in an unbounded queue with no backpressure. This means that...

After a quick look at generated JSON, it looks like the exported macros (and their doc comments) are not included. But I'm not familiar enough with the `save-analysis` part of...