Val Markovic

@abingham For the identifier completer, there's a cap of max 10 completion strings returned. It needs to be there, otherwise ycmd can end up sending you _a lot_ of text....

> Would be a nice feature to being able to specify the cap to have more identifiers than 10. Yeah this makes sense. Open an issue on ycmd. > What...

YCM has encountered this issue as well, and the solution was to have [some filetypes in the blacklist by default.](https://github.com/Valloric/YouCompleteMe#the-gycm_filetype_blacklist-option)

Thanks for your interest in contributing! :) As you've noticed, upstream hamcrest-rust seems dead; I'm open to PRs. As a general rule, I do not break backwards compatibility unless absolutely...

@joshburkart Looked at the PR. I think your API is quite nice actually. Thanks for sending that out in the first place! The more people out there thinking about better...

Let's do it. :)

Why not just do this? ```rust fn test() { assert_that!(&S::new(42), eq(&S::new(42))); assert_that!(&S::new(42), not(eq(&S::new(41)))); } ``` Another approach: ```rust #[derive(PartialEq, Debug)] #[cfg_attr(test, derive(Clone))] // Notice we derive Clone in test builds...

I think the variant with calls to clone is fine and pretty readable. Anyone familiar with Rust will be familiar with what `.clone()` does so I don't expect it would...

Interestingly, disabling every extension _except_ this one does not lead to the input latency spike on gibberish but it _does_ still lead to 100% CPU usage. My guess is that...

My intuition was correct: this extension pairs badly with the [Vim emulation extension](https://marketplace.visualstudio.com/items?itemName=vscodevim.vim). Note that VS Code Vim is an _incredibly_ popular extension. I ran the same experiment with this...