aboutsummaryrefslogtreecommitdiff
path: root/docs/dev/README.md
Commit message (Collapse)AuthorAgeFilesLines
...
* Explain inline testsAleksey Kladov2020-06-101-0/+11
|
* Dev docs nitsLaurențiu Nicola2020-06-081-7/+7
|
* Don't @ people in commit messagesAleksey Kladov2020-06-081-0/+8
|
* Preconditions styleAleksey Kladov2020-06-081-0/+20
|
* IDE APIAleksey Kladov2020-06-081-0/+7
|
* Document certain invariantsAleksey Kladov2020-06-061-0/+27
|
* Document import styleAleksey Kladov2020-06-061-0/+21
|
* BufgixVeetaha2020-06-031-3/+3
|
* Start documenting review processAleksey Kladov2020-06-031-1/+104
|
* Fix names of launch configuration in dev docsYuki Kodama2020-05-201-2/+2
|
* Use RA_LOG instead of RUST_LOG for loggingAleksey Kladov2020-05-111-1/+1
| | | | | | RUST_LOG might be set up for debugging the user's problem, slowing down rust-analyzer considerably. That's the same reason why rustc uses RUSTC_LOG.
* vscode: move docks about syntax tree to dev/README.mdveetaha2020-04-021-0/+10
|
* Rename config value for server PathAleksey Kladov2020-02-181-1/+1
|
* Rename the binary to rust-analyzerAleksey Kladov2020-02-181-9/+9
|
* Replace ra_cli mentionsLaurențiu Nicola2020-02-171-4/+4
|
* Fix RA_PROFILE typo in docsLaurențiu Nicola2020-02-171-2/+2
|
* docs: Freshen docs for prebuilt binaries and raLspServer settingVeetaha2020-02-091-2/+9
|
* Docs cleanupsFlorian Diebold2020-02-081-6/+6
|
* Freshen Architecture.md documentAleksey Kladov2020-01-291-0/+4
|
* Freshen dev docs a tiny bitsAleksey Kladov2020-01-291-48/+36
|
* Update READMEAlexander Ekdahl2019-11-301-3/+2
|
* rename ra_ide_api -> ra_ideAleksey Kladov2019-11-271-1/+1
|
* Don't create a separate bin for format hookAleksey Kladov2019-11-181-1/+1
|
* Update rustdoc link pt.2memoryruins2019-10-241-1/+1
|
* rename tools -> xtaskAleksey Kladov2019-10-171-5/+5
|
* Update link to api rustdocsmemoryruins2019-10-141-1/+1
|
* 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
* 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.
* 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
|
* 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
|
* explain how to launch the thingAleksey Kladov2019-03-201-0/+81
|
* remove old contributingAleksey Kladov2019-03-201-0/+6
|
* start dev readmeAleksey Kladov2019-03-201-0/+37