aboutsummaryrefslogtreecommitdiff
path: root/docs/dev
Commit message (Collapse)AuthorAgeFilesLines
* Explain what to do if a release failsLaurențiu Nicola2021-02-011-0/+4
|
* Update lsp-extension.md hashEdwin Cheng2021-01-281-1/+1
|
* Update docEdwin Cheng2021-01-281-1/+1
|
* Merge #7457bors[bot]2021-01-261-0/+8
|\ | | | | | | | | | | | | | | | | | | 7457: Add no-buffering file logging and wait for a debugger option. r=vsrs a=vsrs Adds two command line flags: `--no-buffering` and `--wait-dbg`. Not sure if someone else needs this, but personally I found both flags extremely useful trying to figure out why RA does not work with Visual Studio. Or better to say why Visual Studio does not work with RA. Co-authored-by: vsrs <[email protected]>
| * Add RA_WAIT_DBG and docsvsrs2021-01-251-0/+8
| |
* | Make always-assert crate reusableAleksey Kladov2021-01-261-1/+1
| |
* | Document design labelAleksey Kladov2021-01-261-0/+4
|/
* Fix typo in style guideLaurențiu Nicola2021-01-251-3/+4
|
* Fix RA_LOG example in dev docsLaurențiu Nicola2021-01-251-1/+1
|
* Promote marksAleksey Kladov2021-01-221-6/+16
|
* Style: use the right stringAleksey Kladov2021-01-221-0/+12
|
* Include `countme` crate to count important data structures.Aleksey Kladov2021-01-211-0/+3
|
* Avoid intermediate collectionsAleksey Kladov2021-01-201-1/+33
|
* Don't show runnable suggestions for other filesAleksey Kladov2021-01-201-0/+3
| | | | | It't be actually great to have these once we have run anything dialog, but for run the thing at point it makes sense to show a limited set.
* Introduce more appropriate assertion mechanismAleksey Kladov2021-01-141-0/+5
| | | | | | | rust-analyzer is a long-running program, so we *should* handle assertion failures. See also https://www.sqlite.org/assert.html.
* Encourage gifsAleksey Kladov2021-01-111-0/+2
|
* Use T! for bool keywordsLaurențiu Nicola2021-01-101-0/+21
|
* typoAleksey Kladov2021-01-071-23/+23
|
* Styleguide readabilityAleksey Kladov2021-01-071-63/+115
|
* Document `std::ops` styleAleksey Kladov2021-01-071-1/+9
|
* Merge #7195bors[bot]2021-01-071-1/+1
|\ | | | | | | | | | | | | | | 7195: Update remaining serverPath references r=lnicola a=lnicola Fixes https://github.com/rust-analyzer/rust-analyzer/pull/7156#issuecomment-755487667 Co-authored-by: Laurențiu Nicola <[email protected]>
| * Update remaining serverPath referencesLaurențiu Nicola2021-01-071-1/+1
| |
* | Change <|> to $0 - RebaseKevaundray Wedderburn2021-01-071-1/+1
|/
* Merge #7068bors[bot]2021-01-032-1/+14
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7068: Add VSCode command to view the hir of a function body r=theotherphil a=theotherphil Will fix https://github.com/rust-analyzer/rust-analyzer/issues/7061. Very rough initial version just to work out where I needed to wire everything up. @matklad would you be happy merging a hir visualiser of some kind? If so, do you have any thoughts on what you'd like it show, and how? I've spent very little time on this thus far, so I'm fine with throwing away the contents of this PR, but I want to avoid taking the time to make this more polished/interactive/useful only to discover that no-one else has any interest in this functionality. ![image](https://user-images.githubusercontent.com/1974256/103236081-bb58f700-493b-11eb-9d12-55ae1b870f8f.png) Co-authored-by: Phil Ellison <[email protected]>
| * Address review suggestion, fix tidy testsPhil Ellison2021-01-012-1/+14
| |
* | Improve commit message styleAleksey Kladov2020-12-281-0/+12
|/
* Update docs/dev/README.mdAleksey Kladov2020-12-161-1/+1
| | | Co-authored-by: Lukas Wirth <[email protected]>
* Document new permissionsAleksey Kladov2020-12-161-0/+14
|
* Add `#` to canonical test exampleAleksey Kladov2020-12-151-4/+4
|
* Normalize spelling to American EnglishAleksey Kladov2020-12-101-0/+1
|
* fix typo of README in devDaiki Ihara2020-12-081-1/+1
|
* Document statelessness invariantAleksey Kladov2020-12-031-0/+16
|
* fix typos in syntax.mdJakob Hellermann2020-11-171-2/+2
|
* Latest LSP 3.16 protocolkjeremy2020-11-161-2/+2
| | | | Pulls in https://github.com/gluon-lang/lsp-types/pull/186
* add open Cargo.toml actionAnatol Liu2020-11-131-2/+27
|
* Switch to upstream protocol for resolving code actionAleksey Kladov2020-11-101-25/+1
| | | | | | Note that we have to maintain custom implementation on the client side: I don't see how to marry bulitin resolve support with groups and snippets.
* don\t indent testsAleksey Kladov2020-11-061-0/+26
|
* Update docs/dev/style.mdAleksey Kladov2020-11-021-1/+1
| | | Co-authored-by: Laurențiu Nicola <[email protected]>
* Document doer object anti-patternAleksey Kladov2020-11-021-0/+54
|
* Update client install command in dev docsLaurențiu Nicola2020-10-271-1/+1
|
* Update debugging.mdAdrian Stanciu2020-10-221-1/+1
|
* Document change of 'cargo' Runnable kind in lsp-extensions.mdIgor Aleksanov2020-10-161-0/+3
|
* Expand code order sectionAleksey Kladov2020-10-161-11/+50
|
* Document awkward namesAleksey Kladov2020-10-151-0/+12
|
* Cleanup alloc adviceAleksey Kladov2020-10-151-0/+7
|
* Style: default over newAleksey Kladov2020-10-141-0/+25
|
* Introduce S-actionable and S-unactionable labelsAleksey Kladov2020-10-141-1/+6
| | | | | | | | | | I've noticed that a significant fraction of issues are inert. They are valid, acknowledged and useful, but effectively can't be fixed for variety of reasons (no reproduction, dependencies on some other issues, no review capacity, etc). Marking issues that can be fixed by just applying some elbow grease seems useful!
* Add reminder to update lsp-extensions.mdAleksey Kladov2020-10-141-0/+10
|
* Fix send->sent typoZac Pullar-Strecker2020-10-081-7/+7
|
* Document the protocol extensionZac Pullar-Strecker2020-10-081-1/+12
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-26 18:24:18 +0000