Loïc Damien

As discussed in https://github.com/dzamlo/rust-bitfield/pull/21#issuecomment-496318709 This would replaced the `from into`

With this option, you will still get the `BitRange` implementation, the `Debug` implementation and the fields getter and setter.

We should add a way to call arbitrary method on the value before returning it. For example to do endianness conversion. I don't know yet how it would look like.

Especially the fact that it comes for free only with `BitRange`

I recall that at some point I concluded that the fixes introduced by https://github.com/rust-lang/rust/pull/42913 could simplify part of the code of this crate. I don't know if this is still...

we could also simplify the code by transforming invocation without visibility to `pub(self)`. We may want to wait for the `vis` fragment specifier to become stable (https://github.com/rust-lang/rust/issues/41022).

Old issue are not included in codeclimate.json and this mark them as resolved in Gitlab

2

The generated `codeclimate.json` only include new issues. The issue with that, is that the old issue that are not resolved are marked as resolved in the Merge request even if...

Newline in the issue message are not escaped when building the json

4

If the message of an issue contain a newline (`\n`) character, it isn't escaped line when the `codeclimate.json` file is generated. This means that the value for the "check_name" key...

Use one read thread and one write thread

5

On my machine, when benchmarking withe the provided docker image (make build && make run) show a significant speed improvement. Other small benchmarking seems to show a very small improvement.