Richard

> The s flag is the dotAll flag, and isn’t in ES6/ES2015 - it’s in ES2018. The `s` flag is also enabled by default in master. As a side note,...

This likely stems from this PR https://github.com/microsoft/ChakraCore/pull/6232 The method for tracking register lifetimes in the JIT was changed there and this test case seems to be hitting a code path...

In my testing of jitting Async Generators I have hit a very similar looking assert jitting `yield*` my fix was this: https://github.com/microsoft/ChakraCore/pull/6465/commits/d1a02a553fc60089fb8d2959b9dd9838682a346f A set of changes that add several lines...

Could this be related to these which hit similar assertions: #6181 #6487 Extra note: done some more digging into these 3 issues - in all 3 it seems that the...

A bit more thinking about this - #6181 is exactly the same idea - inlining a regex related call, adding the coercion methods and losing the register tracking for bailout....

The bailout in this one is a BailOnImplicitCall - the optimisation becomes invalid if converting to a string has an implicit call (that may have a side effect). The optimised...

I had guessed wrong on the PR that introduced this bug. I've now done git bisect to locate it. This crash was introduced by this PR: https://github.com/chakra-core/ChakraCore/pull/5854 The PR worked...

Interestingly if you reverse the order of parameters `Math.max(a,NaN)` you get the expected output. Also noted that this repros in both Master and release 1.11. The implementation of Math.max was...

> Hello there i am new to open source contribution. Where can i find this piece of code in your repository? Have a look at the links in my previous...

@anshul2807 it's a good first issue if you want to take it - though not sure if @Abdullah17m was already intending to take it? Don't want two people working on...