Luca
Luca
@JosephTLyons I would be happy to contribute if it’s a simple fix, any pointer to what I should be looking at to make this work?
@SomeoneToIgnore wow! thanks, now I can use zed. Just missed rustc, this works: ```json "lsp": { "rust-analyzer": { "initialization_options": { "rustc": { "source": "discover" ...snip ``` I wonder why adding...
> Mh, sounds kinda hard, because when there is any kind of mutability or randomness involved, we can still end up with identical expressions that evaluate to completely different things...
Makes sense @rustbot claim
i think some parts of this lints overlap with eq_op lint, does it make sense to implement it as separate lint or expand that?
[maker](https://crates.io/crates/marker_uitest) seems to make it work with a wrapper around uitests.
also a better diff when running the test would be so much appreciated I opened this https://github.com/Manishearth/compiletest-rs/issues/284 but @Manishearth [mentioned](https://github.com/Manishearth/compiletest-rs/issues/281#issuecomment-1721568033) that the crate is not actively maintained so no luck...
doesn't seem to allow it, maybe could be [added](https://docs.rs/ui_test/latest/ui_test/enum.Error.html#variant.OutputDiffers) but the default one is better than `compiletest` already. I think rust really needs a better UI test framework...
https://github.com/oli-obk/ui_test/issues/205
no idea, but I can give it a try.