Sebastian Markbage d16750f5c8 Set on havoced object should target the receiver, not the own object (#2338) ... Summary: In case the havoced object has a setter on it. This is fixes this particular bug but it's also useful to be able to pass the correct receiver to properties.js rather than unwrapping it like we do now. This will be evident in a follow up PR. This also lets emitPropertyAssignment deal with abstract values which is a common pattern and will become more common with widened objects. Pull Request resolved: https://github.com/facebook/prepack/pull/2338 Differential Revision: D9035746 Pulled By: sebmarkbage fbshipit-source-id: 2abb1a3eb047de1739dec94259a803c4c45e416d		2018-07-27 15:09:10 -07:00
..
error-handler	Run Prettier for serializer tests too (#2234)	2018-07-11 03:55:11 -07:00
react	Add shape model functionality to React components (#2320)	2018-07-25 11:27:47 -07:00
residual	Run Prettier for serializer tests too (#2234)	2018-07-11 03:55:11 -07:00
serializer	Set on havoced object should target the receiver, not the own object (#2338)	2018-07-27 15:09:10 -07:00
source-maps	Run Prettier for serializer tests too (#2234)	2018-07-11 03:55:11 -07:00
std-in	fix #1239 - Command-line based syntax errors now print location	2017-12-18 13:56:26 -08:00
test262@e9a5a7f918	Update test262 submodule hash	2018-07-06 14:25:54 -07:00