danielrainer
danielrainer
The previous version of the code just uses the first executable it finds in the JSON output of cargo. This is problematic because multiple executables might be produced, for example...
Hi, thank you for this project! I recently tried to get debugging to work with Vimspector. It works well now that I found out how to do it, but finding...
At the moment, local docs are not updated when running `rust-analyzer.openDocs`, which can result in unintentionally reading outdated documentation. I suggest to provide a way of automatically building docs before...
This addresses #2098. This code is just a quick demonstration of part of the functionality I would like to have, not finished code. No docs have been updated to indicate...
Having to configure a block directly inside the main config file is fine when the block is never reused, but in scenarios where the same block configuration is reused in...
https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#snippet_syntax Some snippets already work well, but I noticed that when auto-filling the arms of a `match`, the placeholders don't get parsed properly. For example, for the following completing the...
I have code which builds up some constraints over bitvectors and then tries to minimize the value of one of them. Code to reproduce the issue can be found at...
It would be great if flog could use the `log.date` config from the relevant git config file by default, if no format is explicitly specified. This would automatically use peoples'...
One common way to indicate failure of a process it to exit non-zero. Prior to these changes, littlecheck did not care about the exit code, aside from showing information about...
If a test exits non-zero, littlecheck will report success, as long as all `CHECK` and `CHECKERR` comments were matched. I'm not sure if this is intentional, but it certainly is...