| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Use RUSTC_BOOTSTRAP=1 instead of +nightly when discovering rust_cfgs ↵ | Lukas Wirth | 2021-05-08 | 1 | -32/+31 |
| | | | | | throughs cargo | ||||
| * | Discover rustc_cfg through unstable cargo options | Lukas Wirth | 2021-05-08 | 1 | -7/+31 |
| | | |||||
| * | some clippy::performance fixes | Matthias Krüger | 2021-03-15 | 1 | -1/+1 |
| | | | | | | | | use vec![] instead of Vec::new() + push() avoid redundant clones use chars instead of &str for single char patterns in ends_with() and starts_with() allocate some Vecs with capacity to avoid unneccessary resizing | ||||
| * | Avoid blocking the main loop when editing Cargo.toml | Aleksey Kladov | 2021-01-18 | 1 | -0/+34 |
| I've noticed a bunch of "main loop too long" warnings in console when typing in Cargo.toml. Profiling showed that the culprit is `rustc --print cfg` call. I moved it to the background project loading phase, where it belongs. This highlighted a problem: we generally use single `cfg`, while it really should be per crate. | |||||
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |