Weird behaviour with Structs

I feel the following is an issue because the full code compiles, which indicates it is a valid construction. I don’t know much about structs in C++ though.

Anyway, the following is handled strangely (can see easier in Atom).

struct Scanner {

  vector<CategoryDescription> category_descriptions = {
    {FOO, FOO, FOO},
    {FOO, FOO, FOO}
  };

  map<string, TokenType> tokens = {
    {"(", BEGIN_INLINE_MATH},
    {")", END_INLINE_MATH},
  };

  map<char, Category> catcodes = {
    {'\\',   ESCAPE_CATEGORY},
    {'{',    BEGIN_CATEGORY}
  };

};

The first item is scoped differently to the others, and reordering them or adding fields above does not affect this (whatever the first is is still scoped differently).

It also folds incorrectly; folding line 1 folds up until the semicolon of the vector, when it should be folding the entire struct.

[maxbrunsfeld]

Fixed on Atom master! I hate to see Tree-sitter failing you while you’re working on a Tree-sitter parser (guessing from your example). Thanks for raising this!

[thomasjo]

~It’s not related to structs. The problem is that list initialization is not currently supported by the grammar.~ Nope, @Aerijo was correct all along.