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.

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

The wasm-bindgen code refers to oldtime::Duration and is failing #483

Merged
merged 2 commits into from
Sep 26, 2020

Conversation

quodlibetor
Copy link
Contributor

wasm only works on new-enough rust that we can unconditionally use the crate
keyword in that method, so let's try that.

#286 (comment)

@CryZe
Copy link
Contributor

CryZe commented Sep 25, 2020

Looks like this fixes my build issues 👍

@quodlibetor quodlibetor merged commit 70432bc into chronotope:main Sep 26, 2020
@quodlibetor quodlibetor deleted the fix-wasm-duration branch September 26, 2020 01:17
@quodlibetor
Copy link
Contributor Author

@CryZe thanks for verifying, and sorry it broke your build!

@jhpratt
Copy link

jhpratt commented Sep 26, 2020

Looks like the comment regarding semver isn't actually implemented?

@benesch
Copy link
Contributor

benesch commented Sep 26, 2020

If we're going to get pedantic about SemVer, breaking changes are permitted in minor or patch releases pre 1.0. It's Cargo that violates the SemVer spec on this point.

lopopolo added a commit to artichoke/artichoke that referenced this pull request Sep 27, 2020
See chronotope/chrono#478 which was released as chrono v0.4.16.

This PR pegs the minimum chrono to 0.4.17 to pull in a wasm fix from
chronotope/chrono#483.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants