Anything that isn't going to make it into v2. I also wouldn't hold your breath for any of this. These are ideas and they aren't making it into v2 likely beause it's not clear if they are actually possible, and even if they are if it would make any sense.
Ideas:
Anything that isn't going to make it into v2. I also wouldn't hold your breath for any of this. These are ideas and they aren't making it into v2 likely beause it's not clear if they are actually possible, and even if they are if it would make any sense.
Ideas:
specta::function::*andspecta::specta. I wish I never stablised this but it's relied on by Tauri and we can no longer remove it cleanly (bring back Dropfunctionfrom core #432)DataTypelayer. This would likely require the removal or rethinking ofTypesas it currently prevents things being static as callingT::definition(types)on a dependant type has side-effects onTypeswhich isn't'static.TypesasTypeMapin crate root which is relied on by Tauri so we were stuck with it for v2Serialize/Deserializeimplementation. I would argue this is a misuse of crate-features as they are intended to be "addative" (due to how Cargo enables them for all users of the crate in the dependency tree) but still would be nice to handle them.