-
Notifications
You must be signed in to change notification settings - Fork 30
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
Side-effect on std::convert::Into<_>
introduced in 0.1.12
#22
Comments
Could it be an issue with |
Hum... not sure what you mean by transitive dependencies. I'm looking at |
@behnam I mean, could adding flame as a dependency change the versions of other dependencies in your project? |
@behnam: any update on this? I don't think that this is the fault of bincode. |
No updates here, @TyOverby . I guess it's a version conflict for serde_derive stuff, but I don't find it. |
If this still repros for you, could you send me the contents of your Cargo.lock file before and after? Also try building |
Thanks, @TyOverby. Here are the files: |
Also, I disabled default |
your before/after cargo.lock.toml files are identical |
Closing due to inactivity; please reopen if this is still an issue. |
As the
0.1.12
update yesterday, I noticed that building lib unit tests is failing inunicode-bidi
withflame_it
feature. I went back and minimized the changes for the break, which actually reduced to onlyextern crate flame;
, and only happening for=0.1.12
.Here's the commit causing error on a stable
unicode-bidi
build: behnam/rust-unicode-bidi@6e6fc78Here's the error:
from https://travis-ci.org/behnam/rust-unicode-bidi/jobs/243806493#L259
I have no idea how flame can cause this in a module that doesn't use any of the traits. What do you think, @TyOverby ?
The text was updated successfully, but these errors were encountered: