aboutsummaryrefslogtreecommitdiff
path: root/docs/dev
Commit message (Collapse)AuthorAgeFilesLines
...
* | architecture.md: "finish not Y" -> "finish node Y"eupn2019-08-071-1/+1
|/ | | Is this a typo?
* document upgrade processAleksey Kladov2019-07-291-0/+2
| | | | closes #1615
* Overhaul installation processAleksey Kladov2019-07-271-4/+4
| | | | | | | The new commands are $ cargo install-ra --client-code $ cargo install-ra --server --jemalloc
* fix: spellingMartin Grönlund2019-07-151-1/+1
|
* Remove executeCommandProvider: apply_code_action.Michael Bolin2019-07-111-2/+0
| | | | | | | | | | | | | | | | | | | This appears to have been introduced ages ago in https://github.com/rust-analyzer/rust-analyzer/commit/be742a587704f27f4e503c50f549aa9ec1527fcc but has since been removed. As it stands, it is problematic if multiple instances of the rust-analyzer LSP are launched during the same VS Code session because VS Code complains about multiple LSP servers trying to register the same command. Most LSP servers workaround this by parameterizing the command by the process id. For example, this is where `rls` does this: https://github.com/rust-lang/rls/blob/ff0b9057c8f62bc4f8113d741e96c9587ef1a817/rls/src/server/mod.rs#L413-L421 Though `apply_code_action` does not seems to be used, so it seems better to delete it than to parameterize it.
* Document the VS Code extension test frameworkRyan Cumming2019-06-261-0/+19
|
* add analysis-bench to benchmark incremental analysisAleksey Kladov2019-06-161-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Can be used like this: ``` $ cargo run --release -p ra_cli -- \ analysis-bench ../chalk/ \ --complete ../chalk/chalk-engine/src/logic.rs:94:0 loading: 225.970093ms from scratch: 8.492373325s no change: 445.265µs trivial change: 95.631242ms ``` Or like this: ``` $ cargo run --release -p ra_cli -- \ analysis-bench ../chalk/ \ --highlight ../chalk/chalk-engine/src/logic.rs loading: 209.873484ms from scratch: 9.504916942s no change: 7.731119ms trivial change: 124.984039ms ``` "from scratch" includes initial analysis of the relevant bits of the project "no change" just asks the same question for the second time. It measures overhead on assembling the answer outside of salsa. "trivial change" doesn't do an actual salsa change, it just advances the revision. This test how fast is salsa at validating things.
* fixed wrong links againzjy2019-06-121-4/+4
|
* fixed linkszjy2019-06-111-5/+5
|
* Add to LSP featureskjeremy2019-04-231-1/+1
|
* fix docsAleksey Kladov2019-04-211-1/+1
|
* filter by timeAleksey Kladov2019-04-141-2/+4
|
* cleanup syntaxAleksey Kladov2019-04-141-0/+10
|
* Fix issue label link in docs/dev/README.mdpcpthm2019-04-041-1/+1
|
* structure moved to ra_ide_apiSergey Parilin2019-03-251-13/+0
| | | | ra_ide_api_light removed completely
* link docs from dev docs, not from the main readmeAleksey Kladov2019-03-251-1/+5
| | | | If you want to **use** ra, you don't need api docs
* document work listAleksey Kladov2019-03-231-0/+9
|
* describe how do we test thingsAleksey Kladov2019-03-201-1/+26
|
* explain how to launch the thingAleksey Kladov2019-03-203-36/+91
|
* remove old contributingAleksey Kladov2019-03-202-18/+6
|
* start dev readmeAleksey Kladov2019-03-202-0/+37
|
* kill old roadmap: it is completedAleksey Kladov2019-03-201-77/+0
|
* introduce docs dirAleksey Kladov2019-03-206-0/+1006
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 03:26:40 +0000