[vcFormat] `space.withinInitializerListBraces`/`space.withinSquareBrackets` are not heeded inside array initialization

まず、vcFormat と関連する space.withinInitializerListBraces または space.withinSquareBrackets 設定を有効にした .c ファイルで問題を再現します。配列の初期化内にある最初の指示付き初期化子を vcFormat がどのように処理するかを追跡し、その後、フォーマットによって両方の期待される例に示されたスペースが保持されることを確認します。

Environment

• OS and Version: Various (assuming all)
• VS Code Version: 1.117.0
• C/C++ Extension Version: 1.31.5

Bug Summary and Steps to Reproduce

Bug Summary:

When the setting C_Cpp.vcFormat.space.withinInitializerListBraces is set to true, vcFormat fails to add (and will actually remove) a space from between the opening brace and the first designated initializer of all struct members when part of the initialization of an array of structs.

Steps to reproduce:

1. Ensure C_Cpp.vcFormat.space.withinInitializerListBraces is set to true
2. Add the following lines to a .c file:

typedef struct {
    int member_a;
    int member_b;
} MyStruct_t;

MyStruct_t array_of_structs[] = {
    { .member_a = 0, .member_b = 1 },
    { .member_a = 2, .member_b = 3 },
    { .member_a = 4, .member_b = 5 },
};

3. Format the file using vcFormat

Expected behavior:

• The file should not change

Actual result:

typedef struct {
    int member_a;
    int member_b;
} MyStruct_t;

MyStruct_t array_of_structs[] = {
    {.member_a = 0, .member_b = 1 },
    {.member_a = 2, .member_b = 3 },
    {.member_a = 4, .member_b = 5 },
};

The same problem also appears to afflict the first designated initializer of an array with spaces enabled inside square brackets. Here are steps to reproduce:

1. Ensure C_Cpp.vcFormat.space.withinSquareBrackets is set to true
2. Add the following lines to a .c file:

int my_array[3] = {
    [ 0 ] = 100,
    [ 1 ] = 101,
    [ 2 ] = 102,
};

3. Format the file using vcFormat

Expected behavior:

• The file should not change

Actual result:

int my_array[3] = {
    [0] = 100,
    [ 1 ] = 101,
    [ 2 ] = 102,
};

Configuration and Logs

Configurations vary; the pertinent configuration options are mentioned above.

Logs will be provided if deemed necessary. I believe this should be very easily reproduced.

Other Extensions

No response

Additional context

No response