Lukas Wirth
Lukas Wirth
Though these errors aren't parsing errors in rustc, but type inference so I think this is overall a bug in the parser for us. I can see the `const` blocks...
Ah whoops I was testing it differently by accident
You can go ahead and ask if you'd like
Turns out pretty much nothing works inside that macro, not even hover. The macro does get expanded though...
A quick test seems to not really change the times for me when running with and without the wrapper (though that might be because `cargo check` gets skipped due to...
Opened a zulip topic in the t-cargo stream to see if we can work on this from the cargo side of things as our own options here are rather limited...
Picking one of the `CARGO_CFG_TARGET_*` ones seems most reasonable, I *could* see someone setting one of the later 3 on their system for something unrelated given their short names (though...
PR https://github.com/rust-lang/rust-analyzer/pull/13010 is up, though I can't test whether it works as I am actually not running into the issue with `anyhow` for some reason.
is this about the textmate grammar used for rust? That is shipped by VSCode itself, not something we are in control of.
Panicking whenever hovering the `Option` here in my current session https://github.com/rust-analyzer/rust-analyzer/blob/516eb40ba5b9d20e59e98185d1b2fcba5599ef7a/crates/base_db/src/fixture.rs#L91 Interestingly enough, the output of the debug prints you added differs on each panic... and if triggered often enough...