facebookarchive/prepack
1
1
Fork 0
mirror of https://github.com/facebookarchive/prepack.git synced 2024-11-23 23:13:43 +03:00
Code Issues Projects Releases Wiki Activity
Page: Marking an object as simple
Pages
Compiler assumptions Effects Fuzzer Home Marking an object as simple Optimized Functions Optimized function PP0002 PP0003 PP0004 PP0005 PP0006 PP0007 PP0008 PP0009 PP0010 PP0011 PP0012 PP0013 PP0014 PP0015 PP0016 PP0017 PP0018 PP0019 PP0020 PP0021 PP0022 PP0023 PP0024 PP0025 PP0026 PP0027 PP0028 PP0029 PP0030 PP0031 PP0032 PP0033 PP0034 PP0035 PP0036 PP0037 PP0038 PP0040 PP0041 PP0043 PP0045 PP1001 PP1002 PP1003 PP1004 PP1005 PP1006 PP1007 PP1008 PP1009 PP8000 PP9000 Partially unknown object Prepack Concepts Prepack diagnostics React Compiler Research papers citing Prepack Suggested reading Tips and tricks on how to debug things as a Prepack developer Unknown Abstract function value Unknown Abstract value Well behaved property
2 Marking an object as simple
Dominic Gannaway edited this page 2018-08-30 01:29:23 +01:00

An abstract object that is returned from an environmental model holds lots of dangers for Prepack, which can result in a lot of error messages and a failure to successfully run Prepack.

If the object is known to be quite simple, it can be marked as such by calling the __makeSimple global function with the object as its argument.

This informs Prepack that getting or setting a property on the object, or converting it to a string or number, or checking if it defines a property or if it is an instance of a constructor function, will neither throw an exception nor make any visible changes to the heap.

Furthermore, simple objects are assumed to not have any symbolic getters/setters, such as [Symbol.hasInstance].