…negative index

…rvative) fix for this issue relied on marking scopes as containing 'with'. But because block scopes are created lazily, we can miss the opportunity to mark a scope. Instead, implementing a more accurate fix that marks symbols that are referenced from within 'with' statements as needing scope objects if they are closure-captured.

…off - Internal

…king failure

…bjectDictionary type

This is the case where array's length is bigger than head segment's length.
Fixed that by putting proper check.

We are incorrectly assuming an object literal to be a pattern. Because we have one local variable when we are parsing the member short we have changed the state.
Fixed that by restoring it back.

In ReverseHelper call to ReallocateNonLeafLastSegmentIfLeaf can throw which leaves the lastUsedSegment wrongly pointed to
the unlinked segment.
Fixed that by putting AutoFailFast error.

The peephole optimizer fails to invalidate both arguments to XCHG
instructions, which can lead subsequent passes (notably copy propagation)
to refer to the XCHG op's second arg, assuming it will get that register's
original value.  Fixed that by invalidating both arguments.
# Conflicts:
#	test/Bugs/rlexe.xml

…expression symbol is captured
If a split scope happens because of the function expression being captured then the param scope may not have any locals in closure as the function expression symbol belongs to the function expression scope. In this case we don't have to instantiate the param scope in split scope.

We used this memcpy to put the references on the stack so that the
GC wouldn't free them; the compiler figured out that it could take
the memcpy and the stack buffer out completely (by spec). Actually
passing it around fixes this issue.

CustomExternalObjects can override the enumeration operations to
have side effects. In such a case, an object can be passed to an
invocation of JSON::Stringify, leading to stack values being used
inappropriately.