Luca Barbato
Luca Barbato
I started looking at it and indeed this would be a great feature.
It needs people writing the glue code and a rebase over the current dav1d asm, if you feel like trying :)
> Does this also easily work with cross compilation and on more exotic OSes like QNX and VxWorks? The two targets aren't currently supported since I'm taking a conservative approach...
Adding the cargo-c metadata doesn't prevent you from using your custom machinery for custom targets, but makes the life of linux distributors much easier. If you are planning to use...
Your analysis seems correct for all I could see, but I'd defer to @barrbrain for informed opinions :)
A route having `Vec` as body produces a quite wrong type: ```diff - type: string - format: binary + type: array + items: + type: integer + format: int32 +...
My workaround is to create a struct with an explicit schema with `utoipa::openapi::Type::String` with a specific Binary format.
Maybe just having some `cargo xtask` applets to generate man pages and install could be enough?
How should it map?
Just I saw less activity and I might have another slice of time to help a little.