aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * Refactor primitive types into more orthogonal representationyanchith2019-03-224-144/+155
|/
* Merge #1013bors[bot]2019-03-2215-24/+149
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1013: Fuzz reparsing and fix found bugs r=matklad a=pcpthm Add fuzz test for reparsing which: - Checks reparsing doesn't panic and validate result syntax tree. - Checks that incremental reparsing produces the same syntax tree as full reparse. - Check for that errors are the same as full reparsing is disabled because errors are less important than syntax tree and produce failures which I couldn't figure out how to fix immediately (FIXME comment). I guess the current input generation is inefficient but still found several bugs: - Arithmetic overflow (negative result on an unsigned type). I changed the signature of `SyntaxError::add_offset` to solve this problem. - When reparsing a leaf, the token of the leaf can be joined to the next characters. Such case was not considered. - UNDERSCORE token was not produced when text length is exactly 1 (not a reparsing bug). - When reparsing a block, *inner* curly braces should be balanced. i.e. `{}{}` is invalid. - Effects of deleting newlines were not considered. Co-authored-by: pcpthm <[email protected]>
| * Fix reparsing failure when removing newlinepcpthm2019-03-212-0/+14
| |
| * Fix reparsing bug on "{}{}"pcpthm2019-03-212-1/+5
| |
| * Completely ignore errors for reparse fuzzpcpthm2019-03-211-1/+0
| |
| * Use template text to improve reparse fuzzingpcpthm2019-03-211-1/+5
| |
| * Fix lexer not producing right token on "_"pcpthm2019-03-212-0/+1
| |
| * Fix reparsing bug when lex result is differentpcpthm2019-03-213-2/+17
| |
| * Improve reparse fuzz testpcpthm2019-03-211-1/+13
| |
| * Fix an arithmetic overflow in reparserpcpthm2019-03-213-5/+11
| |
| * Add fuzz test for reparsingpcpthm2019-03-214-1/+64
| |
| * Refactor parser fuzz testingpcpthm2019-03-215-16/+23
| |
* | Merge #1014bors[bot]2019-03-221-2/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | 1014: Don't execute cargo watch when information message is dismissed r=matklad a=pcpthm I think most information messages on `VSCode` have such behavior. Co-authored-by: pcpthm <[email protected]>
| * | Don't execute cargo watch when popup is dismissedpcpthm2019-03-221-2/+2
| |/
* | Merge #988bors[bot]2019-03-2212-318/+377
|\ \ | |/ |/| | | | | | | | | | | 988: Consolidate Ty variants into a new variant Ty::Apply r=matklad a=flodiebold This gets us a lot closer to Chalk. It also introduces a lot of boilerplate, though, especially when matching :/ A lot of this can probably be refactored to be nicer, though. Co-authored-by: Florian Diebold <[email protected]>
| * Assert in apply_substs that the number of parameters doesn't changeFlorian Diebold2019-03-212-2/+7
| | | | | | | | ... and fix a small bug revealed by that.
| * Rename name field to ctor as wellFlorian Diebold2019-03-215-29/+29
| |
| * Some more doc commentsFlorian Diebold2019-03-211-2/+12
| |
| * TypeName => TypeCtorFlorian Diebold2019-03-217-98/+98
| |
| * Remove the old variants replaced by Ty::ApplyFlorian Diebold2019-03-2112-404/+266
| |
| * Add Ty::ApplyFlorian Diebold2019-03-211-1/+177
| |
| * Represent FnPtr and Tuple using SubstsFlorian Diebold2019-03-213-27/+33
|/
* Merge #1011bors[bot]2019-03-213-301/+298
|\ | | | | | | | | | | | | | | 1011: cleanup r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * cleanupAleksey Kladov2019-03-211-68/+73
| |
| * move diagnostics to ide_apiAleksey Kladov2019-03-213-258/+250
|/
* Merge #1010bors[bot]2019-03-213-16/+31
|\ | | | | | | | | | | | | | | | | | | | | 1010: Change enableCargoWatchOnStartup to have three states r=matklad a=vipentti This fixes #1005. Defaults to `ask` which prompts users each time whether to start `cargo watch` or not. `enabled` always starts `cargo watch` and `disabled` does not. Co-authored-by: Ville Penttinen <[email protected]>
| * Change enableCargoWatchOnStartup to have three statesVille Penttinen2019-03-213-16/+31
|/ | | | | | | This fixes #1005. Defaults to `ask` which prompts users each time whether to start `cargo watch` or not. `enabled` always starts `cargo watch` and `disabled` does not.
* Merge #1002bors[bot]2019-03-211-33/+122
|\ | | | | | | | | | | | | | | 1002: Fill partial fields r=matklad a=c410-f3r Fixes #992 Co-authored-by: Caio <[email protected]>
| * Improve performance and orderingCaio2019-03-201-21/+15
| |
| * Fill partial fieldsCaio2019-03-201-32/+127
| |
* | Merge #997bors[bot]2019-03-218-62/+180
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 997: Improve filtering of file roots r=matklad a=vipentti `ProjectWorkspace::to_roots` now returns a new `ProjectRoot` which contains information regarding whether or not the given path is part of the current workspace or an external dependency. This information can then be used in `ra_batch` and `ra_lsp_server` to implement more advanced filtering. This allows us to filter some unnecessary folders from external dependencies such as tests, examples and benches. Relates to discussion in #869 Co-authored-by: Ville Penttinen <[email protected]>
| * | Move actual include logic to ProjectRootVille Penttinen2019-03-215-53/+69
| | | | | | | | | | | | | | | This way the two IncludeRustFiles implementations can simply call the ProjectRoots' methods, so that the include logic is in one place.
| * | Improve filtering of file rootsVille Penttinen2019-03-206-62/+164
| |/ | | | | | | | | | | | | | | | | `ProjectWorkspace::to_roots` now returns a new `ProjectRoot` which contains information regarding whether or not the given path is part of the current workspace or an external dependency. This information can then be used in `ra_batch` and `ra_lsp_server` to implement more advanced filtering. This allows us to filter some unnecessary folders from external dependencies such as tests, examples and benches.
* | Merge #1003bors[bot]2019-03-204-20/+62
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 1003: make Name::new private r=flodiebold a=matklad This maybe is overengineering, but it seems cool to keep names completely opaque. r? @flodiebold Co-authored-by: Aleksey Kladov <[email protected]>
| * | make Name::new privateAleksey Kladov2019-03-204-20/+62
| | |
* | | Merge #1008bors[bot]2019-03-207-401/+420
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 1008: Move extend selection to ra_ide_api r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | move extend selection from ra_ide_api_light to ra_ide_apiAleksey Kladov2019-03-206-401/+403
| | |
| * | introduce Analysis::from_single_fileAleksey Kladov2019-03-201-0/+17
|/ /
* | Merge #1000bors[bot]2019-03-2011-462/+687
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 1000: Clean up some documentation debt r=Xanewok a=matklad Co-authored-by: Aleksey Kladov <[email protected]> Co-authored-by: bjorn3 <[email protected]>
| * | Update README.mdbjorn32019-03-201-1/+1
| | | | | | | | | Co-Authored-By: matklad <[email protected]>
| * | 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
| | |
| * | fixesAleksey Kladov2019-03-202-2/+2
| | |
| * | start dev readmeAleksey Kladov2019-03-202-0/+37
| | |
| * | kill old roadmap: it is completedAleksey Kladov2019-03-201-77/+0
| | |
| * | document some nice thingsAleksey Kladov2019-03-201-0/+36
| | |
| * | document assistsAleksey Kladov2019-03-201-48/+203
| | |
| * | sadly, we support only a single language atmAleksey Kladov2019-03-201-1/+1
| | |
| * | fix linksAleksey Kladov2019-03-201-2/+2
| | |