You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-3
Original file line number
Diff line number
Diff line change
@@ -402,7 +402,7 @@ While .proto and JSON files require the full library (about 18kb gzipped), prett
402
402
403
403
Static code, on the other hand, requires just the minimal runtime (about 5.5kb gzipped), but generates additional, albeit editable, source code without any reflection features.
404
404
405
-
Where `new Function(...)` is supported (it usually is), there is no difference performance-wise as the code generated statically is pretty much the same as generated at runtime.
405
+
There is no difference performance-wise as the code generated statically is pretty much the same as generated at runtime.
406
406
407
407
Building
408
408
--------
@@ -493,8 +493,6 @@ Note that JSON is a native binding nowadays and as such is about as fast as it p
493
493
* For entirely bogus values encoders intentionally rely on runtime errors to be thrown somewhere down the road.
494
494
* Quite a bit of V8-specific profiling is accountable for everything else.
495
495
496
-
Note that code generation requires `new Function(...)` (basically `eval`) support and that an equivalent but slower fallback will be used where unsupported.
497
-
498
496
You can also run [the benchmark](https://github.com/dcodeIO/protobuf.js/blob/master/bench/index.js) ...
0 commit comments