Luca Barbato

Results 667 comments of Luca Barbato

rust: need a way to pass ldflags to rustc?

The order should be the opposite, I think. Check what's the rustc final invocation passing -v to cargo

rust: need a way to pass ldflags to rustc?

that I can see they are not present.

rust: need a way to pass ldflags to rustc?

I guess part of the problem is that host and target are the same x86_64 to add additional confusion to the issue ...

rust: musl libc - cannot compile rust for x86_64

I wonder when that variable went away...

rust: musl libc - cannot compile rust for x86_64

That should still work, the cargo home should be empty when you start...

rust: musl libc - cannot compile rust for x86_64

Looks like so

Nested generic parameters must be manually inlined

Right now I'm having the opposite problem, the generic type is inlined even if I use `#[schema(inline = false)]` on it.

Nested generic parameters must be manually inlined

I have a situation like ```rust #[derive(ToSchema)] struct A { #[schema(inline = false)] a: Vec } #[derive(ToSchema)] struct B { #[schema(inline = false)] b: T, } ``` T is inlined...

Nested generic parameters must be manually inlined

Even simpler reproducer: ```rust #[derive(Debug, Serialize, ToSchema)] enum E { } #[derive(Debug, Serialize, ToSchema)] struct S { total: i32, #[schema(inline = false)] severities: HashMap, } ``` S inlines E

The generated spec for an Option field is unpleasant and breaks swift-openapi-generator

It also triggers https://github.com/acacode/swagger-typescript-api/issues/991