Brace matching does not account for inactive regions

[parindawm]

Issue Type: Bug

please make test.cpp file using following code
#undef x
int main()
{
int a=0, b=0,c=0;
#ifndef x
if(b==2){
if(a==0){
}
else
#else
if(c==1){
#endif
a=1;
}// wrong matching
return 0;
}// wrong machine

Observe wrong bracket pairing at commented places. "// wrong machine"

Extension version: 0.23.1
VS Code version: Code 1.34.0 (a622c65b2c713c890fcf4fbf07cf34049d5fe758, 2019-05-15T21:59:37.030Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 2808)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: unavailable_off surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: unavailable_off
Load (avg)	undefined
Memory (System)	15.89GB (7.41GB free)
Process Argv
Screen Reader	no
VM	0%

[parindawm]

screen capture disabling the Other extensions (other than vscode-cpptools )

[sean-mcmanus]

Our extension doesn't currently implement brace matching. The behavior is coming from VS Code's handling, which doesn't understand that the other brace is in an inactive region (which our extension adds).

[sean-mcmanus]

This appears to be being tracked by microsoft/language-server-protocol#672

[vliedel]

This appears to be being tracked by microsoft/language-server-protocol#672

Though that issue is a feature request for brace matching, while these mismatches also lead to an incorrect index, as the function afterwards is no longer seen as a function. Which to me, seems like a bug. What would be the right way to report this?

[Colengms]

We have the following feature request open against VS Code, which would allow us to address this: microsoft/vscode#163954