Luca Barbato

I tried to use the type alias but it does not work for me. utoipa keeps generating the invalid ref `#/components/schemas/T`

I cannot reproduce the problem with `rustc 1.79.0 (129f3b996 2024-06-10)` on an Apple M2.

Once https://github.com/rust-lang/rust/issues/124225 hits stable `paste` can be migrated away, but paste does not have vulnerabilities.

I'd wait till it is completely oxidized since as it is now we'd still need nasm and a C compiler, but it is definitely something to consider. Sorry for not...

That I could see you do need a C compiler at least for one target https://github.com/memorysafety/rav1d/blob/main/build.rs#L362 ``` rust cc::Build::new() .files([&"tools/compat/getopt.c"]) .include("include/compat") .debug(cfg!(debug_assertions)) .compile(&getopt); ``` Details aside, is there a compelling...

`nasm-rs` and `cc-rs` do their work, but they tend to be more brittle than they should in my experience. I have few ideas on how to address at least some...

- because `meson` has most of the logic to support asm built in and the additional logic to support special stuff like the `gas-preprocessor` isn't that trivial to redo. -...

The [last comment](https://internals.rust-lang.org/t/discussion-adding-grammar-information-to-procedural-macros-for-proper-custom-syntax-support-in-the-toolchain/21496/33) in the thread sounds a fairly straightforward way to tackle it. Does anybody see anything against the approach of offloading the macros to an external program based...

Thank you!

That means RVA23U64+Zacas would be needed, I guess.