aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | Merge #2964bors[bot]2020-02-011-8/+14
|\ \ | | | | | | | | | | | | | | | | | | | | | 2964: Improve responsiveness of the cargo check status label r=matklad a=lnicola This is still not ideal because the label displays the crate that was just checked, not the one that's currently being checked. But it should give the impression of being faster. Co-authored-by: Laurențiu Nicola <[email protected]>
| * | Improve responsiveness of the cargo check status labelLaurențiu Nicola2020-01-311-8/+14
| | |
* | | Merge #2972bors[bot]2020-02-011-0/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2972: Prevent child cargo process from messing with our stdin r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Prevent child cargo process from messing with our stdinAleksey Kladov2020-02-011-0/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | By default, `spawn` inherits stderr/stdout/stderr of the parent process, and so, if child, for example does fcntl(O_NONBLOCK), weird stuff happens to us. Closes https://github.com/rust-analyzer/lsp-server/pull/10
| | |
| \ \
*-. \ \ Merge #2963 #2967bors[bot]2020-02-012-2/+30
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2963: Emacs fixes r=matklad a=flodiebold - use provided environment for runnables (finally set `RUST_BACKTRACE`) - implement `selectAndApplySourceChange` so auto-import works :slightly_smiling_face: cc @brotzeit 2967: Disable optimizations for some build-time crates r=matklad a=lnicola This speeds up a release build on my laptop from 4m 13s to 3m 33s. It's a bit disappointing, but we don't get perfect parallelism during the build. The non-RA dependencies finish building around 72s as opposed to 112s. Co-authored-by: Florian Diebold <[email protected]> Co-authored-by: Florian Diebold <[email protected]> Co-authored-by: Laurențiu Nicola <[email protected]>
| | * | | Disable optimizations for some build-time cratesLaurențiu Nicola2020-01-311-0/+19
| | |/ /
| * | | Implement support for selectAndApplySourceChange (auto import) in EmacsFlorian Diebold2020-01-311-1/+9
| | | |
| * | | Fix env in emacs runnables supportFlorian Diebold2020-01-311-1/+2
| |/ /
* | | Merge #2970bors[bot]2020-02-013-6/+8
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2970: [VSCode] Fix syntax highlighting r=matklad a=bjorn3 Fixes #2969 Fixes #2971 Co-authored-by: bjorn3 <[email protected]>
| * | | Tsfmtbjorn32020-02-011-2/+2
| | | |
| * | | Fix seedrandom in packaged extensionbjorn32020-02-012-3/+3
| | | | | | | | | | | | | | | | Fixes #2971
| * | | [VSCode] Fix syntax highlightingbjorn32020-02-011-1/+3
|/ / / | | | | | | | | | Fixes #2969
* | | Merge #2965bors[bot]2020-02-011-6/+10
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2965: Improve auto import message r=kiljacken a=lnicola Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | Improve auto import messageLaurențiu Nicola2020-01-311-6/+10
| |/ /
* | | Merge #2966bors[bot]2020-01-311-2/+2
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 2966: Fix extra parentheses warnings r=kjeremy a=lnicola Co-authored-by: Laurențiu Nicola <[email protected]>
| * | Fix extra parentheses warningsLaurențiu Nicola2020-01-311-2/+2
|/ /
* | Merge #2960bors[bot]2020-01-311-4/+6
|\ \ | | | | | | | | | | | | | | | | | | | | | 2960: Small cleanup r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | Small cleanupAleksey Kladov2020-01-311-4/+6
|/ /
* | Merge #2946bors[bot]2020-01-301-2/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | 2946: updating nvim_lsp usage for rust_analyzer r=matklad a=matu3ba The other option is invalid and a working version depends on [PR](https://github.com/neovim/nvim-lsp/pull/107) Co-authored-by: Jan <[email protected]>
| * | updating nvim_lsp usage for rust_analyzerJan2020-01-291-2/+1
| | |
* | | Merge #2955bors[bot]2020-01-302-697/+689
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2955: :arrow_up: rust r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Switch Cargo.lock to the new formatAleksey Kladov2020-01-301-696/+688
| | | |
| * | | :arrow_up: rustAleksey Kladov2020-01-301-1/+1
| | | |
* | | | Merge #2954bors[bot]2020-01-301-0/+3
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 2954: Add a FIXME note r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Add a FIXME noteAleksey Kladov2020-01-301-0/+3
|/ / /
* | | Merge #2920bors[bot]2020-01-301-2/+18
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2920: Better handle illformed node id from metadata r=matklad a=edwin0cheng In some rare cases, deps node-id from cargo-metadata do not match its version-id, which cause a panic in `cargo-workspace.rs`. This PR try to ignore these ill-formed node id from `cargo-metadata`. An alternative is return `Err` in these cases but I think make it resilience is a better choice here. Related #2767 Co-authored-by: Edwin Cheng <[email protected]>
| * | | Ignore illform node id from metadataEdwin Cheng2020-01-281-2/+18
| | | |
* | | | Merge #2953bors[bot]2020-01-301-20/+20
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2953: Update crates r=kjeremy a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * | | | Update cratesJeremy Kolb2020-01-301-20/+20
|/ / / /
* | | | Merge #2952bors[bot]2020-01-301-21/+8
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2952: Simplify fixture parsing r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Simplify fixture parsingAleksey Kladov2020-01-301-21/+8
|/ / / /
* | | | Merge #2895bors[bot]2020-01-291-46/+71
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2895: Rewrite ra_prof's profile printing r=michalt a=michalt This changes the way we print things to first construct a mapping from events to the children and uses that mapping to actually print things. It should not change the actual output that we produce. The new approach two benefits: * It avoids a potential quadratic behavior of the previous approach. For instance, for a vector of N elements: ``` [Message{level: (N - 1)}, ..., Message{level: 1}, Message{level: 0}] ``` we would first do a linear scan to find entry with level 0, then another scan to find one with level 1, etc. * It makes it much easier to improve the output in the future, because we now pre-compute the children for each entry and can easily take that into account when printing. Signed-off-by: Michal Terepeta <[email protected]> Co-authored-by: Michal Terepeta <[email protected]>
| * | | A couple of small improvements to ra_prof printingMichal Terepeta2020-01-291-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | Based on suggestions from @matklad. Signed-off-by: Michal Terepeta <[email protected]>
| * | | Rewrite ra_prof's profile printingMichal Terepeta2020-01-221-46/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changes the way we print things to first construct a mapping from events to the children and uses that mapping to actually print things. It should not change the actual output that we produce. The new approach two benefits: * It avoids a potential quadratic behavior of the previous approach. For instance, for a vector of N elements: ``` [Message{level: (N - 1)}, ..., Message{level: 1}, Message{level: 0}] ``` we would first do a linear scan to find entry with level 0, then another scan to find one with level 1, etc. * It makes it much easier to improve the output in the future, because we now pre-compute the children for each entry and can easily take that into account when printing. Signed-off-by: Michal Terepeta <[email protected]>
* | | | Merge #2943bors[bot]2020-01-292-20/+53
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2943: Re-sync queries for memory usage measurnment r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Re-sync queries for memory usage measurnmentAleksey Kladov2020-01-292-20/+53
| | | | |
* | | | | Merge #2942bors[bot]2020-01-291-29/+17
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2942: Properly select a target for auto importing r=matklad a=SomeoneToIgnore Fixes https://github.com/rust-analyzer/rust-analyzer/issues/2932 The corresponding test has the caret placed in the beggining of the document despite the import inserted, but I don't thing I should fix it here: * in real life, there's some text written before the import and for those cases the caret behaves normally * it's a separate functionality that needs to be refactored anyway later (the `auto_import_text_edit`) Co-authored-by: Kirill Bulatov <[email protected]>
| * | | | Properly select a target for auto importingKirill Bulatov2020-01-291-29/+17
|/ / / /
* | | | Merge #2941bors[bot]2020-01-292-38/+45
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2941: Freshen Architecture.md document r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Freshen Architecture.md documentAleksey Kladov2020-01-292-38/+45
| | | | |
* | | | | Merge #2940bors[bot]2020-01-292-48/+38
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2940: Freshen dev docs a tiny bits r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Freshen dev docs a tiny bitsAleksey Kladov2020-01-292-48/+38
| | | | |
* | | | | Merge #2939bors[bot]2020-01-291-20/+19
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2939: Simplify fixture parsing r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Simplify fixture parsingAleksey Kladov2020-01-291-20/+19
| | | | |
* | | | | Merge #2938bors[bot]2020-01-291-1/+1
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2938: Fix long loop timeout r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Fix long loop timeoutAleksey Kladov2020-01-291-1/+1
|/ / / /
* | | | Merge #2937bors[bot]2020-01-292-5/+26
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2937: Parse cargo output a line at a time. r=kiljacken a=kiljacken We previously used serde's stream deserializer to read json blobs from the cargo output. It has an issue though: If the deserializer encounters invalid input, it gets stuck reporting the same error again and again because it is unable to foward over the input until it reaches a new valid object. Reading a line at a time and manually deserializing fixes this issue, because cargo makes sure to only outpu one json blob per line, so should we encounter invalid input, we can just skip a line and continue. The main reason this would happen is stray printf-debugging in procedural macros, so we still report that an error occured, but we handle it gracefully now. Fixes #2935 Co-authored-by: Emil Lauridsen <[email protected]>
| * | | | Change error output to make a bit more senseEmil Lauridsen2020-01-291-2/+6
| | | | |
| * | | | Parse cargo output a line at a time.Emil Lauridsen2020-01-292-5/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We previously used serde's stream deserializer to read json blobs from the cargo output. It has an issue though: If the deserializer encounters invalid input, it gets stuck reporting the same error again and again because it is unable to foward over the input until it reaches a new valid object. Reading a line at a time and manually deserializing fixes this issue, because cargo makes sure to only outpu one json blob per line, so should we encounter invalid input, we can just skip a line and continue. The main reason this would happen is stray printf-debugging in procedural macros, so we still report that an error occured, but we handle it gracefully now. Fixes #2935
* | | | | Tweak readmeAleksey Kladov2020-01-291-3/+2
| | | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-24 01:30:06 +0000