the trait bound implicit_clone::unsync::IMap<_, _>: From<indexmap::IndexMap<K, V>> is not satisfied
#3659
Comments
|
+1 this issue, currently trying out yew with the getting started example per documentation and the same error appears, even if i remove the dynamic/state parts (e.g. only trying to render an h1). |
|
Sane thing. I have tried a few examples, including those in the docs, and the result is always this crash. Update: this problem does not seem to be there with version Update 2: this commit seems to be the problem, no? 71b0f20 |
|
This is a problem with |
|
Should we report a bug against indexmap then? |
|
anyone solved ? |
|
Not as far as I am aware. I think somebody needs to open a bug against indexmap. (I haven't had time recently) Anybody know what version of indexmap broke backwards compatibility? |
|
+1 this issue getting this when running the example script in the yew documentation |
|
Not sure this helps, but I did the following, by adding fake indexmap dependancy:
Huh? I verified in each case using "cargo tree" that the yew/indexmap was the expected version. Then I did a "cargo update" (no other changes), which updated indexmap to 2.2.6 everywhere. It still seems to work. So now I am unclear if indexmap 2.2.6 is the solution, or if this is just coincidence. And I haven't been able to test my binary yet (unrelated issue with clippy after updating everything). |
|
It still fails after reverting the version because Cargo.lock will probably probably hold onto the previously set 2.0.1, since it assumes that going from 2.0.0 to 2.0.1 shouldn't be breaking |
|
Thats what I thought too, but "cargo tree" clearly showed the yew -> indexmap dependency was now on 2.0.0. |
Hi everyone! 👋 I would like to collect more feedbacks for yewstack/implicit-clone#51 I tried the example you mentioned here by doing this: Everything seems to be working fine. I couldn't reproduce it. Can anyone give more details or exact steps on how to reproduce it? |
|
Here is a more direct link to the error when I did get it: https://github.com/brianmay/robotica-rust/actions/runs/9261430510/job/25476776874 My project has changed a bit since this problem; I am no longer getting the error. But if I check out the old version, and apply the same change, I get the problem again: git clone https://github.com/brianmay/robotica-rust.git
git checkout 7e024ee
wget https://patch-diff.githubusercontent.com/raw/brianmay/robotica-rust/pull/518.patch
patch -p1 --dry-run < 518.patch
cargo build -p robotica-frontend --target wasm32-unknown-unknownThis gives me the following (note I have direnv+nix configured to install rust; you probably won't see these messages). |
|
Please fix this. This has killed any chance of my org using |
Allowing both indexmap v1 & v2 causes a lot of annoyance when the version of indexmap used by this crate and the one used by other crates in the dependency tree don't match. See also yewstack/yew#3659
Problem
I keep getting this error when I try to update a package like serde_yaml or replace serde_yaml with serde_yml line 216.
This comes from
.../yew-0.21.0/src/html/conversion/into_prop_value.rs
I am somewhat puzzled what is going on here. Perhaps the update of indexmap from 2.0.0 to 2.2.6 changed the API.
Steps To Reproduce
See brianmay/robotica-rust#518
Expected behavior
No errors.
Screenshots
As above.
Environment:
Questionnaire
The text was updated successfully, but these errors were encountered: