Flavien Raynaud

Hmm good point, thanks for raising that. I feel like it should still be an error, as for these two different schemas: ``` "fields": [ {"name": "a", "type": "long"}, {"name":...

Do you have a code snippet causing the serialization issue? 🙂 Serializing a `&[u8]` should give you a `Bytes` object. See [here](https://github.com/flavray/avro-rs/blob/7b820c13a1f25c7fd35850a6fed921aabc3ed103/src/types.rs#L114)

There was a bug in the resolving process that was preventing `Vec` to be interpreted as `Bytes`. I've released `v0.6.5` with a bugfix. The way to go for your case...

@GregBowyer @pavlicekcn Would either of you (or anyone else!) be interested in updating this PR (or opening a new one) to make it in a mergeable/reviewable state? I'm happy to...

It looks like this would go against the [Avro specification](https://avro.apache.org/docs/current/spec.html#Schema+Resolution) (if I understand your request correctly, feel free to correct me if I'm wrong!). I would be inclined to try...

Agreed that would be nice to have. I remember giving some thought to it a few months ago: - Have a new trait: ```rust pub trait AvroSchema { fn avro_schema(&self)...

This looks like one of the recurring issues we've had reported, and still have no fix for this (yet!), after a few attempts :( Issues #61 #95 Previous attempt #90...