v0.4.0

[usbalbin]

v0.4.0

Breaking

• feat(breaking): make FromIteratorFixed more generic #21 Update FromIteratorFixed trait to avoid unnameable iterator type as type paramater in the trait

  - pub trait FromIteratorFixed<I: Iterator, const N: usize> {
  -     fn from_iter_fixed(iter_fixed: IteratorFixed<I, N>) -> Self;
  + pub trait FromIteratorFixed<T, const N: usize> {
  +     fn from_iter_fixed<I: Iterator<Item = T>>(iter_fixed: IteratorFixed<I, N>) -> Self;
    }

Other changes

• Somme cleanning from additionnal clippy lints #22
• fix: nightly flags and clippy warnings #20
• Migrate to use cargo readme #24
• Use cargo readme in ci #25

Thank you

• @Daniel-Aaron-Bloom
• @gwen-lg

[gwen-lg]

perhaps list changes and the fact than can break use ?
In commit and PR descriptions ?

[gwen-lg]

Oh, I'm thinking about it.
Clippy also say "missing documentation for the crate"
from https://rust-lang.github.io/rust-clippy/master/index.html#missing_docs_in_private_items

Perhaps it could be good to have one, to have more information on doc.
But I was not sure about what to say and avoid copy past of Readme or part of it.

[Daniel-Aaron-Bloom]

I mean, you could copy the readme and use something like https://crates.io/crates/cargo-readme to make sure they don't get out of sync.

[usbalbin]

Perhaps there is a better way, but what about using cargo-readme to create a temporary file and something like diff to see if the committed README.md is up to date as part of the ci workflow?

[usbalbin]

Thank you both :)