We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, there
Since ver 0.4.20 (in this commit), chrono makes the js-sys a hard dependency which further depends on Rust's libstd.
js-sys
libstd
This makes chrono no longer compatible with no_std while targeting wasm32-unknown-unknown.
no_std
wasm32-unknown-unknown
We recently found it breaks our downstream project and we have to pin chrono to 0.4.19 in our Cargo.toml to get a workaround.
Should we revert the change? Thanks.
The text was updated successfully, but these errors were encountered:
Does #771 solve the problem?
Sorry, something went wrong.
Yes, v0.4.22 solved the problem. Thanks.
No branches or pull requests
Hi, there
Since ver 0.4.20 (in this commit), chrono makes the
js-sys
a hard dependency which further depends on Rust'slibstd
.This makes chrono no longer compatible with
no_std
while targetingwasm32-unknown-unknown
.We recently found it breaks our downstream project and we have to pin chrono to 0.4.19 in our Cargo.toml to get a workaround.
Should we revert the change? Thanks.
The text was updated successfully, but these errors were encountered: