javascript inline regex

[dna2github]

• VSCode Version: 1.30.2
• OS Version: MacOSX 10.12.6

Seem a fix before: microsoft/vscode#15692
But maybe a little different.

Steps to Reproduce:

• write a js file:

/* regex? */
function test() {
   return /"/.test('xxx"xxx');
}

console.log(test());
a = 3 /*test*/ / parseInt(/.+/.exec('3f23fg')[0]);
console.log(a);

b = 1
a = () => b
2 + (b=2), 3
b = 6
console.log(a(),b);
(b)

if (a === 1) {
   b = 2
} else if (a === 2) b = 3
else b = 4
c = 1
x = a/b/gi; y = /b/gi;

if want to run in node, add a line to define b and gi, e.g. b = 1; gi = 1;

• open the file in vscode; colored in red and orange:

Monarch Tokens:

   {
      "start_offset": 101,
      "end_offset": 111,
      "type": "regexp.js",
      "value": "/ parseInt"
   },
   {
      "start_offset": 111,
      "end_offset": 112,
      "type": "regexp.escape.control.js",
      "value": "("
   },
   {
      "start_offset": 112,
      "end_offset": 113,
      "type": "regexp.js",
      "value": "/"
   },
   {
      "start_offset": 113,
      "end_offset": 114,
      "type": "delimiter.js",
      "value": "."
   },
   {
      "start_offset": 116,
      "end_offset": 117,
      "type": "delimiter.js",
      "value": "."
   },
   {
      "start_offset": 117,
      "end_offset": 121,
      "type": "identifier.js",
      "value": "exec"
   },

[sheetalkamat]

This might not be easy to fix because of the way tmLanguage lookup works. We already had issue #3 because of which anything after comment is treated as regexp if it can match completely. Will look into what best action can be taken

[dna2github]

thx, i will track the #3 then.