aboutsummaryrefslogtreecommitdiff
path: root/crates/stdx/src/lib.rs
Commit message (Collapse)AuthorAgeFilesLines
* internal: use API stabilized in 1.52Aleksey Kladov2021-05-061-75/+3
|
* minor: simplifyAleksey Kladov2021-04-261-12/+3
|
* fix: no more Registering progress handler for token rustAnalyzer/Indexing ↵Aleksey Kladov2021-04-201-0/+12
| | | | failed.
* fix: no longer get stuck on windowsAleksey Kladov2021-04-201-7/+8
| | | | | | | reading both stdout & stderr is a common gotcha, you need to drain them concurrently to avoid deadlocks. Not sure why I didn't do the right thing from the start. Seems like I assumed the stderr is short? That's not the case when cargo spams `compiling xyz` messages
* feat: show errors from `cargo metadata` and initial `cargo check` in the ↵Aleksey Kladov2021-04-061-0/+8
| | | | | | status bar closes #3155
* Make always-assert crate reusableAleksey Kladov2021-01-261-1/+1
|
* stave off zombiesAleksey Kladov2021-01-221-0/+1
|
* Fix warnings when running `cargo doc --document-private-items`Joshua Nelson2021-01-181-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These were the warnings previously: ``` warning: could not parse code block as Rust code --> crates/stdx/src/lib.rs:137:9 | 137 | /// ∀ x in slice[..idx]: pred(x) | _________^ 138 | | /// && ∀ x in slice[idx..]: !pred(x) | |____^ | = note: error from rustc: unknown start of token: \u{2200} warning: 1 warning emitted warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = note: `#[warn(broken_intra_doc_links)]` on by default = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: 2 warnings emitted warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = note: `#[warn(broken_intra_doc_links)]` on by default = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: unresolved link to `package` --> crates/base_db/src/input.rs:181:15 | 181 | /// it's [package].name, can be different for other project types or even | ^^^^^^^ no item named `package` in scope | = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` warning: 2 warnings emitted ``` This does *not* fix the following warning, because it is actually rust code and rustdoc is being over eager: ``` warning: Rust code block is empty --> crates/parser/src/grammar.rs:16:5 | 16 | //! ``` | _____^ 17 | | //! // test function_with_zero_parameters 18 | | //! // fn foo() {} 19 | | //! ``` | |_______^ | help: mark blocks that do not contain Rust code as text | 16 | //! ```text | ^^^^^^^ ``` https://github.com/rust-lang/rust/pull/79816 should make this configurable so the warning can be `allow`ed.
* Introduce more appropriate assertion mechanismAleksey Kladov2021-01-141-0/+2
| | | | | | | rust-analyzer is a long-running program, so we *should* handle assertion failures. See also https://www.sqlite.org/assert.html.
* Make printin the backtrace more convenientAleksey Kladov2021-01-141-8/+21
|
* Cleaner APIAleksey Kladov2021-01-101-2/+2
|
* Simplify highlighting infraAleksey Kladov2021-01-081-2/+16
| | | | This also fixes the killer whale bug
* Refactor out JodChildEdwin Cheng2021-01-071-1/+22
|
* Replace RacyFlag with OnceCellAleksey Kladov2020-11-111-29/+1
|
* Add to_upper_snake_case function to stdxIgor Aleksanov2020-10-121-2/+10
|
* Apply suggestions from code reviewIgor Aleksanov2020-10-121-1/+1
| | | Co-authored-by: Lukas Wirth <[email protected]>
* Improve string helpers functionsIgor Aleksanov2020-10-121-1/+5
|
* Add panic_context module for better panic messagesAleksey Kladov2020-09-291-0/+1
|
* Make RacyFlag actually workAleksey Kladov2020-08-181-1/+1
|
* Speedup ty testsAleksey Kladov2020-08-181-1/+29
| | | | Closes #5792
* MinorAleksey Kladov2020-08-181-1/+1
|
* Replace SepBy with ItertoolsAleksey Kladov2020-08-121-64/+1
|
* Fix clippy warningsIgor Aleksanov2020-08-101-2/+2
|
* Use split_once polyfillAleksey Kladov2020-07-301-3/+12
|
* Replace superslice with API on path to stabilizationAleksey Kladov2020-07-231-0/+30
|
* Move stdx macros into submoduleAleksey Kladov2020-07-131-19/+2
|
* Profiling tweaksAleksey Kladov2020-07-111-0/+2
|
* More principled indentation trimming in fixturesAleksey Kladov2020-06-231-0/+82
|
* Slightly better nameAleksey Kladov2020-06-231-1/+1
|
* Speedup VFS::partitionAleksey Kladov2020-06-191-1/+0
| | | | | | | | | | The task of `partition` function is to bin the flat list of paths into disjoint filesets. Ideally, it should be incremental -- each new file should be added to a specific fileset. However, preliminary measurnments show that it is actually fast enough if we just optimize this to use a binary search instead of a linear scan.
* Use split1 when formatting function signature paramsAaron Loucks2020-06-031-0/+5
|
* Use snippets in add functionAleksey Kladov2020-05-201-0/+8
|
* Move snake case method to heckKirill Bulatov2020-05-031-0/+14
|
* Move timeit to stdxAleksey Kladov2020-04-101-1/+15
|
* Check for eprintln on CIAleksey Kladov2020-04-061-0/+15
|
* Fix typoAleksey Kladov2020-03-301-1/+1
|
* Nice string formattingAleksey Kladov2020-03-281-1/+1
|
* Start stdxAleksey Kladov2020-03-281-0/+75
This crate will hold everything to small to be worth publishing
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 19:34:15 +0000