Currently, we fail on the first error. This is mildly annoying if any sort of error occurs. I think it is possible to yield multiple compile_error!s from the macro and that would be ideal, at the very least one per field, since parsing of field attributes can break.
It would also be nice, if possible, to have the macro still generate the builder function on the original struct, returning a "never" type (can't be ! yet, so add an empty enum to bauer::__private) to remove the Foo::builder function not found error.
Currently, we fail on the first error. This is mildly annoying if any sort of error occurs. I think it is possible to yield multiple
compile_error!s from the macro and that would be ideal, at the very least one per field, since parsing of field attributes can break.It would also be nice, if possible, to have the macro still generate the
builderfunction on the original struct, returning a "never" type (can't be!yet, so add an empty enum tobauer::__private) to remove theFoo::builderfunction not found error.