Zachary Kohnen

Having the default workspace resolver as v1 creates confusion in workspaces with all crates using `edition = "2021"`. Telling the user that the resolver might not match their expectation can...

I might also just be using the crate wrong

Yah, thats what I have started to do. Thanks for all your work on it its such a great crate.

I can reproduce this on the latest web demo aswell: https://user-images.githubusercontent.com/14093962/167803740-fd00cd72-bc70-4130-9c4c-ab648914f492.mp4

It does allow for dioxus to setup the wasm runtime for users and let them just focus on their code while allowing more technical users to override the defaults. But...

How would this implementation differ/be better than something like this: ```rs use std::fmt::Debug; use itertools::Itertools; fn cartesian_power(iterator: I) -> impl Iterator where T: Debug + Clone, I: Iterator + Clone,...

dlopen could also gate it behind a `derive` feature much like serde does if the macros are meant to be optional

My audio output is not mono. The output logic most probably is selecting the wrong output format.

This would also be useful to be able to enforce descriptions of arguments for functions

Another solution could be to enable a way to make a type that implements `Display` to be usable as a GraphQLType