rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2022-03-21	Replace write! with direct calls	Laurențiu Nicola	-4/+4

2021-11-05	Replace some String usages with SmolStr in completions	Lukas Wirth	-16/+13

2021-10-14	a few clippy fixes	Milo	-0/+4

2021-07-20	internal: add simple smoke test for project model	Aleksey Kladov	-1/+16
	Our project model code is rather complicated -- the logic for lowering from `cargo metadata` to `CrateGraph` is fiddly and special-case. So far, we survived without testing this at all, but this increasingly seems like a poor option. So this PR introduces a simple tests just to detect the most obvious failures. The idea here is that, although we rely on external processes (cargo & rustc), we are actually using their stable interfaces, so we might just mock out the outputs. Long term, I would like to try to virtualize IO here, so as to do such mocking in a more principled way, but lets start simple. Should we forgo the mocking and just call `cargo metadata` directly perhaps? Touch question -- I personally feel that fast, in-process tests are more important in this case than any extra assurance we get from running the real thing. Super-long term, we would probably want to extend our heavy tests to cover more use-cases, but we should figure a way to do that without slowing the tests down for everyone. Perhaps we need two-tiered bors system, where we pull from `master` into `release` branch only when an additional set of tests passes?
2021-06-21	Improve completion of cfg attributes	Jamie Cunliffe	-0/+20
	The completion of cfg will look at the enabled cfg keys when performing completion. It will also look crate features when completing a feature cfg option. A fixed list of known values for some cfg options are provided. For unknown keys it will look at the enabled values for that cfg key, which means that completion will only show enabled options for those.
2021-06-19	Implement a config override for the default #[cfg(test)] in cargo crates	Jade	-0/+1
	Fixes crates which vanish when the 'test' cfg atom is set. Fix #7243. Fix #9203. Fix #7225.
2021-06-19	Fix libcore not being included in rust-lang/rust module tree	Jade	-1/+15
	If you are opening libcore from rust-lang/rust as opposed to e.g. goto definition from some other crate which would use the sysroot instance of libcore, a `#![cfg(not(test))]` would previously have made all the code excluded from the module tree, breaking the editor experience. This puts in a slight hack that checks for the crate name "core" and turns off `#[cfg(test)]`.
2021-06-13	tree-wide: make rustdoc links spiky so they are clickable	Jade	-1/+1

2021-05-07	internal: expose cfg attrs from hir::Crate	Aleksey Kladov	-1/+1

2020-11-17	Remove dead code	Aleksey Kladov	-6/+0

2020-10-23	cfg: move tests to separate file	Jonas Schievink	-0/+2
	that way we don't have to re-check the entire project when a test is changed
2020-10-22	Fix typo	Jonas Schievink	-1/+1

2020-10-22	Implement DNF-based `#[cfg]` introspection	Jonas Schievink	-0/+110

2020-10-21	Simplify cfg representation	Jonas Schievink	-15/+7

2020-08-13	Rename ra_cfg -> cfg	Aleksey Kladov	-0/+51