aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | Update comment for pop_and_injectPaul Daniel Faria2020-06-231-2/+2
| | | | | | | | | | | | Co-authored-by: Leander Tentrup <[email protected]>
| * | | Update injection mechanism and stop injecting through highlight element, ↵Paul Daniel Faria2020-06-2314-218/+239
| | | | | | | | | | | | | | | | switch to more general new highlight tag, generic
| * | | Add punctuation highlighting for highlighting punctuation in doctests, fix ↵Paul Daniel Faria2020-06-2314-225/+228
| | | | | | | | | | | | | | | | highlighting in doctests
| * | | Add default color and opacity for documentation and injected, respectively, ↵Paul Daniel Faria2020-06-237-0/+14
| | | | | | | | | | | | | | | | in the html generator
| * | | Add support for marking doctest items as distinct from normal code, add ↵Paul Daniel Faria2020-06-239-34/+47
| | | | | | | | | | | | | | | | default tag to all doctest elements
* | | | Merge #5014bors[bot]2020-06-2317-2848/+2814
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5014: Use only one code-path for parsing fixtures r=matklad a=matklad This removes leading newlines everywhere, shifting all ranges in tests by one bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Use only one code-path for parsing fixturesAleksey Kladov2020-06-2311-2790/+2751
| | | | | | | | | | | | | | | | | | | | | | | | | This removes leading newlines everywhere, shifting all ranges in tests by one
| * | | | Centralize fixture parsing for assistsAleksey Kladov2020-06-238-60/+65
|/ / / /
* | | | Merge #5008bors[bot]2020-06-231-22/+4
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5008: Remove useless test code r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Remove useless test codeAleksey Kladov2020-06-231-22/+4
|/ / / /
* | | | Merge #5013bors[bot]2020-06-2317-561/+544
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5013: More principled indentation trimming in fixtures r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | More principled indentation trimming in fixturesAleksey Kladov2020-06-2316-558/+541
| | | | |
| * | | | Minor, renameAleksey Kladov2020-06-232-3/+3
|/ / / /
* | | | Merge #5012bors[bot]2020-06-234-9/+9
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5012: Slightly better name r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | Slightly better nameAleksey Kladov2020-06-234-9/+9
|/ / / /
* | | | Merge #5011bors[bot]2020-06-238-375/+273
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 5011: Simplify fixtures r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | ComplicateAleksey Kladov2020-06-232-6/+52
| | | | | | | | | | | | | | | | | | | | Fixing test fallout unfortunately requires more work, we need to do it, but let's merge something at least!
| * | | Docs for FixtureAleksey Kladov2020-06-232-2/+5
| | | |
| * | | Cut problematic dependencyAleksey Kladov2020-06-236-15/+31
| | | |
| * | | Nicer APIAleksey Kladov2020-06-234-73/+75
| | | |
| * | | SimplifyAleksey Kladov2020-06-233-71/+14
| | | |
| * | | SimplifyAleksey Kladov2020-06-235-31/+24
| | | |
| * | | SimplifyAleksey Kladov2020-06-235-85/+27
| | | |
| * | | Drop rarely used fixture functionalityAleksey Kladov2020-06-233-53/+2
| | | |
| * | | Move fixtures to a separate fileAleksey Kladov2020-06-232-288/+292
|/ / /
* | | Merge #4976bors[bot]2020-06-2346-999/+1026
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4976: New VFS r=matklad a=matklad Still a draft, but mostly working already. Co-authored-by: Aleksey Kladov <[email protected]>
| * | | New VFSAleksey Kladov2020-06-2346-999/+1026
|/ / /
* | | Merge #5010bors[bot]2020-06-234-6/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5010: Remove relative-path dependency r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Remove relative-path dependencyAleksey Kladov2020-06-234-6/+1
| | | |
* | | | Merge #5004bors[bot]2020-06-237-4/+49
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5004: Fix panic in split/merge import assists r=matklad a=lnicola Fixes #4368 #4905 Not sure if this is the best solution here. Maybe the `make` functions should be fallible? We generally seem to be playing whack-a-mole with panics in assists, although most of them are `unwrap`s in the assist code. Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | Fix panic in split and merge import assistsLaurențiu Nicola2020-06-237-4/+49
| | | |
* | | | Merge #5002bors[bot]2020-06-233-5/+15
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5002: Fix underflow panic when doctests are at top of file r=Nashenas88 a=Nashenas88 While debugging a comment at the top of a test string, I discovered that the offset calculations could underflow and panic. This only seemed to occur in tests, I assume because it's running a debug mode. The wrapping is quickly fixed later on in release mode, which is why this seems to have gone unnoticed. The new checks ensure the value is always positive or zero. Co-authored-by: Paul Daniel Faria <[email protected]>
| * | | | Fix underflow panic when doctests are at top of filePaul Daniel Faria2020-06-233-5/+15
| | | | |
| | | | |
| \ \ \ \
| \ \ \ \
| \ \ \ \
| \ \ \ \
| \ \ \ \
| \ \ \ \
| \ \ \ \
*-------. \ \ \ \ Merge #4992 #4993 #4994 #4997 #4998bors[bot]2020-06-235-50/+70
|\ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4992: Never disable error logging on the frontend r=matklad a=Veetaha 4993: Make bootstrap error message more informative and better-fitting r=matklad a=Veetaha Now this better fits standard vscode extension activation failure message and suggests enabling verbose logs. ![image](https://user-images.githubusercontent.com/36276403/85321828-ffbb9400-b4cd-11ea-8adf-4032b1f62dfd.png) 4994: Decouple http file stream logic from temp dir logic r=matklad a=Veetaha Followup for #4989 4997: Update manual.adoc r=matklad a=gwutz GNOME Builder (Nightly) supports now rust-analyzer 4998: Disrecommend trace.server: "verbose" for regular users r=matklad a=Veetaha This option has never been useful for me, I wonder if anyone finds regular users can use this for sending logs Co-authored-by: Veetaha <[email protected]> Co-authored-by: Günther Wagner <[email protected]>
| | | | | * | | | | Disrecommend trace.server: "verbose" for regular usersVeetaha2020-06-221-1/+1
| | | | | | | | | |
| | | | * | | | | | Update docs/user/manual.adocGünther Wagner2020-06-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Co-authored-by: Laurențiu Nicola <[email protected]>
| | | | * | | | | | Update manual.adocGünther Wagner2020-06-221-0/+4
| | | | |/ / / / / | | | | | | | | | | | | | | | | | | GNOME Builder (Nightly) supports now rust-analyzer
| | | * / / / / / Decouple http file stream logic from temp dir logicVeetaha2020-06-222-44/+57
| | | |/ / / / /
| | * | | | | | Make bootstrap error message more informative and better-fittingVeetaha2020-06-221-4/+8
| | | | | | | |
| * | | | | | | Never disable error logging on the frontendVeetaha2020-06-221-1/+0
| | |/ / / / / | |/| | | | |
* | | | | | | Merge #4999bors[bot]2020-06-235-13/+174
|\ \ \ \ \ \ \ | |_|_|_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4999: SSR: Allow matching of whole macro calls r=matklad a=davidlattimore Matching within macro calls is to come later and matching of macro calls within macro calls later still. Co-authored-by: David Lattimore <[email protected]>
| * | | | | | SSR: Allow matching of whole macro callsDavid Lattimore2020-06-225-13/+174
| | |_|/ / / | |/| | | | | | | | | | | | | | | | Matching within macro calls is to come later and matching of macro calls within macro calls later still.
* | | | | | Merge #5000bors[bot]2020-06-229-47/+47
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5000: Remove RelativePathBuf from fixture r=matklad a=matklad The paths in fixture are not really relative (the default one is `/main.rs`), so it doesn't make sense to use `RelativePathBuf` here. bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | Remove RelativePathBuf from fixtureAleksey Kladov2020-06-229-47/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The paths in fixture are not really relative (the default one is `/main.rs`), so it doesn't make sense to use `RelativePathBuf` here.
* | | | | | Merge #4989bors[bot]2020-06-221-6/+7
|\ \ \ \ \ \ | |_|_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4989: Hotfix skipping the first chunks of the artifacts r=matklad a=Veetaha Quick hotfix. fixes: #4986, #4987 The stream starts being consumed once we put a handler for `data` event. When extracting `stream.pipeline()` under `withTempFile` in #4963 I didn't move it into the scope too, which due to preliminary awaiting for async operations with the file system allowed for the first chunks of the file to be skipped Co-authored-by: Veetaha <[email protected]>
| * | | | | Hotfix skipping the first chunks of the artifactsVeetaha2020-06-221-6/+7
|/ / / / /
* | | | | Merge #4988bors[bot]2020-06-221-0/+3
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4988: Don't offer to add missing fields of unknown types r=flodiebold a=lnicola Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | | | Don't offer to add missing fields of unknown typesLaurențiu Nicola2020-06-221-0/+3
| |/ / / /
* | | | | Merge #4900bors[bot]2020-06-222-0/+110
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4900: Self variant enum res fix r=BGluth a=BGluth Fixes #4789. This is my first PR for this project, so it's probably worth giving it an extra close look. A few things that I wasn't sure about: - Is `resolve_path` really the best place to perform this check? It seemed like a natural place, but perhaps there's a better place? - When handling the new variant `PathResolution::VariantDef`, I couldn't see an obvious variant of `TypeNs` to return in `in_type_ns` for Unions and Structs. Co-authored-by: BGluth <[email protected]>
| * | | | Enum variants with `Self::[variant]` now resolve (#4879)BGluth2020-06-221-0/+30
| | | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-27 12:51:13 +0000