snapshot

Author: bobzhang

lib/4.06.1/unstable/js_compiler.ml

@@ -110651,8 +110651,10 @@ module E = Js_exp_make
    Note if we inline {!Caml_exceptions.create}, 
    it seems can be useful for optimizations in theory, 
    in practice, it never happen, since the pattern match 
-   never dig into it internally, so maybe {!Obj.set_tag} 
-   is not necessary at all
+   never dig into it internally.
+   Alternative is to create a block `["xx"]` which relies on object identity
+   We try to avoid this, since inlining would break this, this would make reason
+   about the correctness of inlining more difficult
 *)
 let make exception_str  : J.expression = 
   E.runtime_call Js_runtime_modules.exceptions Literals.create [exception_str]
@@ -395508,7 +395510,7 @@ let classify (prog : string) : Js_raw_info.exp =
   match Parser_flow.parse_expression 
     (Parser_env.init_env None prog) false with 
   | (_, Function {
-    id = None;
+    id = _;
     params = (_, {params});
     async = false;
     generator = false;

lib/4.06.1/unstable/js_refmt_compiler.ml

@@ -110651,8 +110651,10 @@ module E = Js_exp_make
    Note if we inline {!Caml_exceptions.create}, 
    it seems can be useful for optimizations in theory, 
    in practice, it never happen, since the pattern match 
-   never dig into it internally, so maybe {!Obj.set_tag} 
-   is not necessary at all
+   never dig into it internally.
+   Alternative is to create a block `["xx"]` which relies on object identity
+   We try to avoid this, since inlining would break this, this would make reason
+   about the correctness of inlining more difficult
 *)
 let make exception_str  : J.expression = 
   E.runtime_call Js_runtime_modules.exceptions Literals.create [exception_str]
@@ -395508,7 +395510,7 @@ let classify (prog : string) : Js_raw_info.exp =
   match Parser_flow.parse_expression 
     (Parser_env.init_env None prog) false with 
   | (_, Function {
-    id = None;
+    id = _;
     params = (_, {params});
     async = false;
     generator = false;

lib/4.06.1/whole_compiler.ml

@@ -393245,8 +393245,10 @@ module E = Js_exp_make
    Note if we inline {!Caml_exceptions.create}, 
    it seems can be useful for optimizations in theory, 
    in practice, it never happen, since the pattern match 
-   never dig into it internally, so maybe {!Obj.set_tag} 
-   is not necessary at all
+   never dig into it internally.
+   Alternative is to create a block `["xx"]` which relies on object identity
+   We try to avoid this, since inlining would break this, this would make reason
+   about the correctness of inlining more difficult
 *)
 let make exception_str  : J.expression = 
   E.runtime_call Js_runtime_modules.exceptions Literals.create [exception_str]
@@ -398996,7 +398998,7 @@ let classify (prog : string) : Js_raw_info.exp =
   match Parser_flow.parse_expression 
     (Parser_env.init_env None prog) false with 
   | (_, Function {
-    id = None;
+    id = _;
     params = (_, {params});
     async = false;
     generator = false;