Re: Disabling nonstandard RegExp functionalities for proper subclasses of RegExp

My 2 cents. I always had the feeling people complaining about `RegExp.$1` and friends never really used them. For instance, your example: ```js /(a)/.exec('a') Object.keys(bar) RegExp.$1 ``` might have side effects but it's also made up and, I believe, not a real-world concern. If you use

Disabling nonstandard RegExp functionalities for proper subclasses of RegExp

Hi, About the bad old nonstandard RegExp functionalities: * `RegExp.prototype.compile()` — currently in Annex B; * `RegExp.$1`, `RegExp.leftContext`, etc. — currently unspecced. Although we could probably not get rid of them for plain regexps, I think it is a good idea to disable them for

Re: Promises, async functions, and requestAnimationFrame, together.

This is definitely interesting stuff. Have you considered rewriting this so that it only uses generators? If you did then you could test natively in Chrome and see if you get the same results. - Matthew Robb On Sat, Apr 23, 2016 at 7:01 PM, /#!/JoePea wrote: > Just to show a