Sebastiano Vigna
Sebastiano Vigna
Legally I can do `bit_field_vec![width, value; len]` or `bit_field_vec![width => value; len]`.
The repo has now the => version. Will release soon. Thank you noticing this, I was working in parallel on 5 releases and a few wrong things slipped in.
It's totally possible we didn't do proper minimization of the dependencies and we forgot something along the way. BTW, do you know of any tool that will do that automatically?...
And, yes, `common_traits` is terrible.
I removed a lot of unused dependencies. It was our mistake not to check before this release. May I ask you before release with this fix to check with a...
Er, unfortunately you'll have to solve the conflicts...
Full coverage tests?
This sometimes was forgotten. If you can (once again...) solve the conflicts...
So that would return some struct implementing BitFieldSlice, and giving a view on the range, right?
Well it's certainly something that should be done. It's also likely we can get away with a support struct in BitFieldSlice. We're all in vacation now but I think it's...