Description
I would like to be able to find out how much buffer space will be required to serialize a given avro_datum_t ... I've started implementing this but wanted to get feedback on the general approach and API.
The details of most of the functions in datum_size.c haven't been updated yet in the attached patch. The rest should be close to working though.
The main point of concern that I have at the moment is that I'm returning an int64_t which, if positive, is the length required and if negative, will be an error condition (like -EINVAL).
Thoughts? Anything else in the attached patch that should change?