mirror of
https://github.com/facebookarchive/prepack.git
synced 2024-11-27 11:57:59 +03:00
Page:
Tips and tricks on how to debug things as a Prepack developer
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
1
Tips and tricks on how to debug things as a Prepack developer
Nikolai Tillmann edited this page 2018-08-16 10:14:21 -07:00
I got an invariant failures with a message similar to "serialized N of M" (where N !== M)
Comment out the invariant in the code (and possibly other subsequently failing invariants) so that Prepack generates code. Look at the debugging output on the console and generated code to identify the problematic values. Look at next section for information how to debug issues around particular values.
What's up with particular values
If you wonder if why a value like _5
got emitted in the way it was, use the CLI arguments
--debugIdentifiers _5 --debugScopes
to get an annotated program and additional debugging output on the console.