Non control-flow keywords

[cynecx]

See microsoft/vscode#108254 (comment) (and rust-lang/rust-analyzer#6137 (comment)).

This does affect even more keywords (other than fn and use):

...
{
                    "comment": "control flow keywords",
                    "name": "keyword.control.rust",
                    "match": "\\b(async|await|break|continue|do|else|for|if|loop|match|move|return|try|where|while|yield)\\b"
                },
...

move and where do not cause control-flow either.

Also this:

rust-syntax/syntaxes/rust.tmLanguage.json

Lines 341 to 346 in e3b83c8

	"comment": "constant declarations",
	"match": "\\b(const)\\s+([A-Z][A-Za-z0-9_]*)\\b",
	"captures": {
	"1": {
	"name": "keyword.control.rust"
	},

contradicts:

rust-syntax/syntaxes/rust.tmLanguage.json

Lines 649 to 652 in e3b83c8

	"comment": "storage keywords",
	"name": "storage.type.rust",
	"match": "\\b(const|enum|extern|let|macro|mod|struct|trait|type)\\b"
	},

EDIT: The same applies to the async keyword, it doesn't cause control-flow, it's merely a specifier/modifier.

The for keyword may not be used as a control-flow keyword, as it can be used in hrtb context (for<'a> ...). Howver, I am not quite sure how the old grammar dealt with that.