Alex
@paulstraw I don't think this whole thing is a good idea. The complexity of the system grows catastrophically. It is no longer a chain of inheritance, but a reverse graph,...
I almost sure there is need to dramatically tune `cargo-playdate` cache and fs-lock used in target dir. In my plan it's probably next after issue 354 _(I don't want to...
If you want to try some, rename [there](https://github.com/boozook/playdate/blob/main/cargo/src/layout/cargo.rs#L104) `.cargo-lock` to something any other. But don't run tests in multiple threads with this change. I'm not sure but prooooooobably can be...
@paulstraw: In the #360 is a fix that you waiting for. But that's a temporary solution and point for change in future. So, I'm not closing this issue until there...
@notpeter, IMHO, main problem is because I creating `cargo::core::compiler::build_context::BuildContext` and it's invalidating your cargo cache. I need `BuildContext` to get actual dependency tree with `playdate.assets` metadata to properly build assets...
#360 published as beta now. I'll close this issue if all is ok there.
@notpeter I’m just clarifying. Is the problem reproduced **without** using `cargo-playdate`?
@paulstraw, do you have any comments or remarks on the implementation?
Nonono, I was just wondering if the `cargo-playdate` is involved in the process **or** if the problem is reproducible using only `cargo check` or `cargo build` or rust-analyzer. > how...
One more workaround - set another target-directory, add argument `--target-dir=./target-pd` for `cargo-playdate`.