Breaking changes

In derived BinWrite implementations, imported variables are now exposed before field variables, to match the way lexical scoping normally works. If an import and a field have the same name, this will cause the import to be shadowed. Previously, the field would be shadowed.

Enhancements

Diagnostic output is improved when using parse_with and map together in an incompatible way.

It is now possible to use a mix of generic and concrete types in BinWrite derives without triggering a type mismatch error.
It is now possible to use the anonymous lifetime '_ within nested types inside an import directive. (#241)
The compiler will no longer panic when verbose-backtrace is enabled and a derived type contains a docblock with a completely empty line. (#263)
Generated code will no longer trigger clippy::unnecessary_fallible_conversions lints.

In derived BinWrite implementations, imported variables are now exposed before field variables, to match the way lexical scoping normally works. If an import and a field have the same name, this will cause the import to be shadowed. Previously, the field would be shadowed.

Diagnostic output is improved when using parse_with and map together in an incompatible way.

It is now possible to use a mix of generic and concrete types in BinWrite derives without triggering a type mismatch error.
It is now possible to use the anonymous lifetime '_ within nested types inside an import directive. (#241)
The compiler will no longer panic when verbose-backtrace is enabled and a derived type contains a docblock with a completely empty line. (#263)
Generated code will no longer trigger clippy::unnecessary_fallible_conversions lints.