Performance regressions in Chrome Beta (74)

[bd82]

No description provided.

[bd82]

Commented on the previous chromium issue here:
https://bugs.chromium.org/p/v8/issues/detail?id=7952

[bd82]

It seems that the heuristics for "fast properties" in V8 have changed recently causing the Chevrotain parsing rules:

 RULE("Array", () => {/* ... */})

Which are saved as properties on the Parser instance to no longer be optimized.

One possible "fix" for this was to save these rules on the prototype of each Parser.

• 18944c9#diff-de68d7bd91aeec21a1d28cc0436d34ab

This however could have been problematic because Chevrotain Parsing rules may have references
to a specific class instance (e.g const $ = this) so saving them on the prototype could cause unexpected errors.

An alternative solution was to "trick" V8 into thinking that the Parser instance is a prototype and thus
ensure fast properties and optimizations are used.
fb714a7