Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

no_std compatibility on target wasm32-unknown-unknown #772

Closed
kvinwang opened this issue Aug 12, 2022 · 2 comments
Closed

no_std compatibility on target wasm32-unknown-unknown #772

kvinwang opened this issue Aug 12, 2022 · 2 comments

Comments

@kvinwang
Copy link

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.

This makes chrono no longer compatible with no_std while targeting 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.
@kvinwang kvinwang changed the title no_std compatible on target wasm32-unknown-unknown no_std compatibility on target wasm32-unknown-unknown Aug 12, 2022
@h4x3rotab
Copy link

Does #771 solve the problem?

@kvinwang
Copy link
Author

Yes, v0.4.22 solved the problem. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@h4x3rotab @kvinwang @esheppa