language-configuration.json lets you define various pairs of brackets
and braces for autoclosing, surrounding selected text with characters,
and, as it turns out, dictating which brackets get colorized by
the native bracket colorizer.

As far as I can tell, putting the block comment brackets inside the
`brackets` field is pointless. We color our comments green anyway,
so the colors don't show anyway. It is true that F# provides
support for nested comment blocks, but we aren't taking advantage
of the color feature anyway (and I'm unsure if it's even possible
to do so).

The block comments should, however, remain in the other fields
that control autocomplete and surrounding selected text.

language-configuration.json lets you define various pairs of brackets
and braces for autoclosing, surrounding selected text with characters,
and, as it turns out, dictating which brackets get colorized by
the native bracket colorizer.

As far as I can tell, putting the block comment brackets inside the
`brackets` field is pointless. We color our comments green anyway,
so the colors don't show anyway. It is true that F# provides
support for nested comment blocks, but we aren't taking advantage
of the color feature anyway (and I'm unsure if it's even possible
to do so).

The block comments should, however, remain in the other fields
that control autocomplete and surrounding selected text.

language-configuration.json lets you define various pairs of brackets
and braces for autoclosing, surrounding selected text with characters,
and, as it turns out, dictating which brackets get colorized by
the native bracket colorizer.

Currently, having `(* *)` inside the `brackets` field is causing the
infix multiplication operator to be treated by the bracket colorizer
as two brackets: an opening `(*` and a closing `)`. Two things happen
here:

* The `(*` does not correspond to a corresponding `*)` bracket, so it
  is treated as unbalanced (hence why that part of the operator is
  colored red).
* Absent any preceding parens in the expression, the `)` is also
  treated as an unbalanced paren and is colored red. This is the
  best case, which colors the entire operator a uniform red. Strange,
  but normal-looking enough that it actually looked intentional to me
  when I first started getting into F#. The multiplication operator is
  weird due to how similar it is to block comments - maybe it's
  supposed to be that way!
* But the bug really gets exposed when there is a preceding paren in
  the expression such as in the expression `(Seq.fold (*) 1 [1;2;3])`.
  In this case, there *is* a balancing paren - the paren that precedes
  `Seq.fold`. Now the multiplication operator is half red (the block
  comment bracket never gets balanced) and half whatever the colorizer
  picks for the two parens. And now the closing paren after `[1;2;3]` is
  unbalanced and made red!

As far as I can tell, putting the block comment brackets inside the
`brackets` field is pointless. We color our comments green anyway,
so the colors don't show anyway. It is true that F# provides
support for nested comment blocks, but we aren't taking advantage
of the color feature anyway (and I'm unsure if it's even possible
to do so).

The block comments should, however, remain in the other fields
that control autocomplete and surrounding selected text.

Background: ionide/ionide-fsgrammar#209

This comes from a comment regarding a pull request that I made on the
ionide-fsgrammar repository, which removes the (* *) bracket pair
from the "brackets" field of language-configuration.json. One issue
with doing this is that we lose the bracket-like indentation that
VSCode provides by default for all bracket pairs.

In other words, when I hit Enter in the following configuration,
cursor location represented by the white block:

    (*█*)

It should indent the cursor and then put the *) on the next line
with the same indentation level as the (* as follows:

    (*
        █
    *)

when I hit Enter with an unaccompanied (*:

    (*█

It should simply indent as follows:

    (*
        █

Lastly, an unaccompanied `*)` should outdent. That is,

        *)█

should become

    *)█

Background: ionide/ionide-fsgrammar#209

This comes from a comment regarding a pull request that I made on the
ionide-fsgrammar repository, which removes the `(* *)` bracket pair
from the "brackets" field of language-configuration.json. One issue
with doing this is that we lose the bracket-like indentation that
VSCode provides by default for all bracket pairs.

In other words, when I hit Enter in the following configuration,
cursor location represented by the white block:

    (*█*)

It should indent the cursor and then put the `*)` on the next line
with the same indentation level as the `(*` as follows:

    (*
        █
    *)

when I hit Enter with an unaccompanied `(*`:

    (*█

It should simply indent as follows:

    (*
        █

Lastly, an unaccompanied `*)` should outdent. That is,

        *)█

should become

    *)█

Background: ionide/ionide-fsgrammar#209

This comes from a comment regarding a pull request that I made on the
ionide-fsgrammar repository, which removes the `(* *)` bracket pair
from the "brackets" field of language-configuration.json. One issue
with doing this is that we lose the bracket-like indentation that
VSCode provides by default for all bracket pairs.

In other words, when I hit Enter in the following configuration,
cursor location represented by the white block:

    (*█*)

It should indent the cursor and then put the `*)` on the next line
with the same indentation level as the `(*` as follows:

    (*
        █
    *)

---

When I hit Enter with an unaccompanied `(*`:

    (*█

It should simply indent as follows:

    (*
        █

---

Lastly, an unaccompanied `*)` should outdent. That is,

        *)█

should become

    *)█

Background: ionide/ionide-fsgrammar#209

This comes from a comment regarding a pull request that I made on the
ionide-fsgrammar repository, which removes the `(* *)` bracket pair
from the "brackets" field of language-configuration.json. One issue
with doing this is that we lose the bracket-like indentation that
VSCode provides by default for all bracket pairs.

In other words, when I hit Enter in the following configuration,
cursor location represented by the white block:

    (*█*)

It should indent the cursor and then put the `*)` on the next line
with the same indentation level as the `(*` as follows:

    (*
        █
    *)

---

When I hit Enter with an unaccompanied `(*`:

    (*█

It should simply indent as follows:

    (*
        █

---

Lastly, an unaccompanied `*)` should outdent. That is,

        *)█

should become

    *)█

Background: ionide/ionide-fsgrammar#209

This comes from a comment regarding a pull request that I made on the
ionide-fsgrammar repository, which removes the `(* *)` bracket pair
from the "brackets" field of language-configuration.json. One issue
with doing this is that we lose the bracket-like indentation that
VSCode provides by default for all bracket pairs.

In other words, when I hit Enter in the following configuration,
cursor location represented by the white block:

    (*█*)

It should indent the cursor and then put the `*)` on the next line
with the same indentation level as the `(*` as follows:

    (*
        █
    *)

---

When I hit Enter with an unaccompanied `(*`:

    (*█

It should simply indent as follows:

    (*
        █

---

Lastly, an unaccompanied `*)` should outdent. That is,

        *)█

should become

    *)█

Background: ionide/ionide-fsgrammar#209 and ionide/ionide-fsgrammar#210

This comes from a comment regarding a pull request that I made on the
ionide-fsgrammar repository, which removes the `(* *)` bracket pair
from the "brackets" field of language-configuration.json. One issue
with doing this is that we lose the bracket-like indentation that
VSCode provides by default for all bracket pairs.

In other words, when I hit Enter in the following configuration,
cursor location represented by the white block:

    (*█*)

It should indent the cursor and then put the `*)` on the next line
with the same indentation level as the `(*` as follows:

    (*
        █
    *)

---

When I hit Enter with an unaccompanied `(*`:

    (*█

It should simply indent as follows:

    (*
        █

---

Lastly, an unaccompanied `*)` should outdent. That is,

        *)█

should become

    *)█

Background: ionide/ionide-fsgrammar#209 and ionide/ionide-fsgrammar#210

This comes from a comment regarding a pull request that I made on the
ionide-fsgrammar repository, which removes the `(* *)` bracket pair
from the "brackets" field of language-configuration.json. One issue
with doing this is that we lose the bracket-like indentation that
VSCode provides by default for all bracket pairs.

Since I'd like to remove the block comment brackets from the
`language-configuration.json` file, this pull request re-adds
the same semantics to the indentation rules.

In other words, when I hit Enter in the following configuration,
cursor location represented by the white block:

    (*█*)

It should indent the cursor and then put the `*)` on the next line
with the same indentation level as the `(*` as follows:

    (*
        █
    *)

---

When I hit Enter with an unaccompanied `(*`:

    (*█

It should simply indent as follows:

    (*
        █

---

Lastly, an unaccompanied `*)` should outdent. That is,

        *)█

should become

    *)█

Background: ionide/ionide-fsgrammar#209 and ionide/ionide-fsgrammar#210

This comes from a comment regarding a pull request that I made on the
ionide-fsgrammar repository, which removes the `(* *)` bracket pair from
the "brackets" field of language-configuration.json. One issue with
doing this is that we lose the bracket-like indentation that VSCode
provides by default for all bracket pairs. This pull request re-adds the
same semantics to the indentation rules.

In other words, when I hit Enter in the following configuration,
cursor location represented by the white block:

    (*█*)

It should indent the cursor and then put the `*)` on the next line
with the same indentation level as the `(*` as follows:

    (*
        █
    *)

---

When I hit Enter with an unaccompanied `(*`:

    (*█

It should simply indent as follows:

    (*
        █

---

Lastly, an unaccompanied `*)` should outdent. That is,

        *)█

should become

    *)█