Sinotov Aleksandr

Okey, for now I use this workaround: ```rust use serde_json::Value; impl for Unite { fn deserialize(deserializer: D) -> Result where D: Deserializer

> You just need to remove `#[serde(flatten)]` ```rust #[derive(Debug, serde::Deserialize)] #[serde(transparent)] struct First { path: Path0, } #[derive(Debug, serde::Deserialize)] #[serde(transparent)] struct Path0 { begin: Box, } #[derive(Debug, serde::Deserialize)] #[serde(transparent)] struct...

Hi @briansmith, any news on this issue?

@mankinskin Greetings again! I don't know it problem of Tokio or Rust, but using riker from your branch gives me about 74-76% higher RAM usage than stock lib.

@mankinskin @leenozara Greetings! Any update on this? I'm using warp/hyper in my project and having two runtimes (`futures::executor::ThreadPool` and `tokio`) not a good idea, and sometimes and sometimes it's just...

> the patch is usable, it is just not using the optimization I mentioned earlier, which would get rid of the overhead of one oneshot channel when using tokio. But...

> @BratSinot the patch is usable, it is just not using the optimization I mentioned earlier, which would get rid of the overhead of one oneshot channel when using tokio....

This is not an option, because schema changes: ```graphql schema { query: QueryRoot mutation: MutationRoot subscription: SubscriptionRoot } # Directs the executor to query only when the field exists. directive...

But if remove `vec` everything fine: ```rust #[derive(Interface)] #[graphql(field(name = "arr", type = "A"))] //

By the way, all issues about `#[Interface]` through `trait` put into cold storage?