aboutsummaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
...
* Do not overwrite lock filekjeremy2021-02-051-1/+1
| | | | | | Use `npm ci` instead of `npm install`. `npm install` will overwrite the lock file if you have a newer npm version than the one that generated the package-lock.json
* Add howtosAleksey Kladov2021-02-051-0/+8
|
* More architecture.mdAleksey Kladov2021-02-041-2/+42
|
* typo fixesKushagra Gupta2021-02-031-4/+4
|
* Grammar fixesKushagra Gupta2021-02-031-20/+20
| | | | | I think line 235 is still wrong, but I am not sure. Is the `crated/tt` in line 252 supposed to be `crates/tt`?
* Fix spelling mistakes in docs/devLukas Wirth2021-02-034-27/+31
|
* Make architecture more informativeAleksey Kladov2021-02-032-201/+317
| | | | Call out boundaries and invariants
* add useless types to the styleguideAleksey Kladov2021-02-021-0/+14
|
* Improve nvim-lsp setup instructionsLaurențiu Nicola2021-02-011-1/+34
|
* 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 #7451bors[bot]2021-01-271-0/+2
|\ | | | | | | | | | | | | | | 7451: rust-analyzer.files.excludeDirs r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * Add config option to ignore directoriesAleksey Kladov2021-01-261-0/+2
| |
* | 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
| |/ |/|
* | Remove the need to manually sync config in package.jsonAleksey Kladov2021-01-261-4/+4
| |
* | Document design labelAleksey Kladov2021-01-261-0/+4
|/
* Fix typo in style guideLaurențiu Nicola2021-01-251-3/+4
|
*-. Merge #7409 #7421bors[bot]2021-01-252-1/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7409: Add References CodeLens. r=matklad a=vsrs Closes #5836 7421: Fix RA_LOG example in dev docs r=lnicola a=lnicola bors r+ Co-authored-by: vsrs <[email protected]> Co-authored-by: Laurențiu Nicola <[email protected]>
| | * Fix RA_LOG example in dev docsLaurențiu Nicola2021-01-251-1/+1
| |/ |/|
| * Add References code lens.vsrs2021-01-231-0/+2
|/ | | | For Struct, Enum, Union and Trait symbols.
* 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-072-3/+3
|\ | | | | | | | | | | | | | | 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-072-3/+3
| |
* | Merge #7184bors[bot]2021-01-071-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | 7184: Changes Cursor Marker To $0 r=matklad a=kevaundray Co-authored-by: Kevaundray Wedderburn <[email protected]>
| * | Change <|> to $0 - RebaseKevaundray Wedderburn2021-01-071-1/+1
| |/
* / Use american spelling for configAleksey Kladov2021-01-071-1/+1
|/ | | | | | | | As per https://github.com/rust-analyzer/rust-analyzer/blob/171c3c08fe245938fb25321394233de5fe2abc7c/docs/dev/style.md#variable-naming Also implement config aliasing, for pain-free settings migrations in the future
* More maintainable configAleksey Kladov2021-01-061-0/+2
| | | | | | | Rather than eagerly converting JSON, we losslessly keep it as is, and change the shape of user-submitted data at the last moment. This also allows us to remove a bunch of wrong Defaults
* Allow `#anchor` linking of config optionsAleksey Kladov2021-01-051-53/+53
|
* Merge #7113bors[bot]2021-01-031-0/+3
|\ | | | | | | | | | | | | | | | | | | 7113: Manual updates r=matklad a=tekul Add some details on how to build the manual and some clarification on how to deal with "proc macro2 warnings. For context, this arose from [this question](https://users.rust-lang.org/t/how-to-disable-rust-analyzer-proc-macro-warnings-in-neovim/53150) on users.rust-lang.org. Co-authored-by: Luke Taylor <[email protected]>
| * Expand contributing "tip" in manual.adocLuke Taylor2020-12-311-0/+3
| | | | | | | | | | | | - Add link to asciidoc website - Explain how to create the generated adoc files from the source code - How to run asciidoctor to generate the manual
* | 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
| | |
* | | Add support for Rust 2021.Mara Bos2021-01-011-1/+1
| |/ |/|
* | Improve commit message styleAleksey Kladov2020-12-281-0/+12
|/
* Update manual.adocHeyward Fann2020-12-241-1/+1
|
* Document, how to view config in effectAleksey Kladov2020-12-231-0/+3
|
* Clean up descriptions for settingsRüdiger Herrmann2020-12-221-13/+13
| | | | | | | | | | | | Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 16:13:09 +0000