diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2021-09-29 17:21:56 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-09-29 17:21:56 +0000 |
| commit | 9e3e98db8ac9374916e76de42e6710dc23caacbc (patch) | |
| tree | c5309385c160d3544e35a664f7cfb9fafa7195cc /src/test/codegen | |
| parent | ee12b0f173c9780df95df801c8d418245da752b2 (diff) | |
| parent | 0dbaf64b12fc2b55144b2a762095d91f2a9f0592 (diff) | |
| download | rust-9e3e98db8ac9374916e76de42e6710dc23caacbc.tar.gz rust-9e3e98db8ac9374916e76de42e6710dc23caacbc.zip | |
Merge #10384
10384: Add vscode native onEnterRules r=matklad,lnicola a=HKalbasi This PR copy onEnterRules configurations [from vscode-rust](https://github.com/rust-lang/vscode-rust/blob/master/src/extension.ts#L287) based on discussion in #6254 I understand that the ideal way is to use parser data for this, and probably all other things that language-config do. But since it can't be enabled (or at least it isn't enabled) by default in vscode, I think this is needed (until onEnter becomes official LSP and get vscode support). People can still configure shortcut and use the parser based onEnter, so it wouldn't harm anyone. Co-authored-by: hamidreza kalbasi <hamidrezakalbasi@protonmail.com>
Diffstat (limited to 'src/test/codegen')
0 files changed, 0 insertions, 0 deletions