Closed mgeisler closed 11 months ago
Maybe. According to downcast's README, "the other one is more actively maintained". However, downcast actually has a more recent release than downcast-rs. Also, I previously attempted to switch to downcast-rs without success. So I don't want to try again absent a compelling reason. And I don't think that reducing Android's vendor branch is compelling enough. After all, a switch like this might increase somebody else's vendor branch.
Maybe. According to downcast's README, "the other one is more actively maintained". However, downcast actually has a more recent release than downcast-rs. Also, I previously attempted to switch to downcast-rs without success. So I don't want to try again absent a compelling reason.
That makes a lot of sense!
And I don't think that reducing Android's vendor branch is compelling enough. After all, a switch like this might increase somebody else's vendor branch.
True :slightly_smiling_face: I will have to look into this myself in case we import mockall: we can carry our own patches to remove the extra dependency if needed.
Hi again, we can close this — I'm going ahead with the import as-is! We're only using downcast-rs a few times in AOSP, so it might be simpler to switch those to use downcast instead.
Hi @asomers,
I'm looking at vendoring mockall to AOSP so that it becomes available for Android Platform development. As part of that, I would need to vendor the dependencies to our
external/rust/crates/
directory.These are the current dependencies, annotated to indicate crates that are not yet in AOSP:
We try to avoid duplicate dependencies in our tree, and I noticed that we have downcast-rs vendored alrady. From looking at the FAQ of downcast, it seems like the two crates are mostly doing the same job.
Would you be up for a PR which switches the dependency to downcast-rs instead?