You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would really look forward to supporting no_std. At first sight it may not seem that big of a refactoring but typify relies on the schemars crate. This is the only crate that does not support support no_std as far as I can tell. At least in it's current stable version. The schemars team is currently working on a v1.0.0 which also brings no_std support. The v1.0.0 has breaking changes resulting in a bigger refactoring for this crate.
Sooner or later, when schemars-v1.0.0 is released, typify needs to upgrade and refactor anyway. Please consider supporting no_std.
The text was updated successfully, but these errors were encountered:
I would really look forward to supporting
no_std
. At first sight it may not seem that big of a refactoring buttypify
relies on theschemars
crate. This is the only crate that does not support support no_std as far as I can tell. At least in it's current stable version. Theschemars
team is currently working on a v1.0.0 which also bringsno_std
support. Thev1.0.0
has breaking changes resulting in a bigger refactoring for this crate.Sooner or later, when
schemars-v1.0.0
is released, typify needs to upgrade and refactor anyway. Please consider supportingno_std
.The text was updated successfully, but these errors were encountered: