Nick Cameron
Nick Cameron
The RLS should work properly with cross-compiled crates, this mostly means working properly with Rustup and Xargo - [ ] - std libs data for correct target (discussed in #88)...
cc #18 - [X] Emacs - https://github.com/emacs-lsp/lsp-mode - https://github.com/joaotavora/eglot - [X] (Neo)vim (https://github.com/autozimu/LanguageClient-neovim) - [x] Eclipse (https://github.com/eclipse/corrosion) - [x] Sublime Text - https://github.com/rust-lang/rust-enhanced - https://github.com/tomv564/LSP - [x] Atom (https://github.com/rust-lang/atom-ide-rust) -...
`unnecessary_unwrap` recommends that `foo.is_some()` in a conditional followed by `foo.unwrap()` should be replaced by an `if let`. That is usually good advice, however, if the `is_some` is just *part* of...
## Motivation Data structures which closely fit a single inheritance model can be very efficiently implemented in C++. Where high performance (both space and time) is crucial there is distinct...
Logging
We do very minimal logging - a total of six locations log any data. Either we should do proper logging, or we should remove those six logging locations and the...
Cleanup is deprecated from v4.0 onwards. I've started implementation (along with async commit lock resolution) but have got a bit bogged down with the retry logic).
This shouldn't be the default since it means doing a lot of work in `drop` and work which can cause errors (and thus double panics), but it would be a...
## For initial release - [x] Introduction (readme, include in rustdoc, check crate root docs) - Public API of main crate - [x] RawClient - [ ] ColumnFamily - [x]...
Currently, we automatically resolve locks and retry (without bumping the start ts which would be unsound). This is ok as a default, but it would be nice to also allow...
Debugging and handling errors is sub-optimal. Our errors are pretty good for the general case, and for just printing an error to a log or whatever, but if you're actually...