clintharris
clintharris
Having the same problem; downgrading to 1.2.0 also fixed it for me. I realize that in some cases performance hit is negligible, but when it comes to this like using...
This is a quick way of converting the floating-point value to an integer (the bitwise operators only work on 32-bit integers, so it causes the 64-bit float to be converted...
The base-3 number system used for timestamps means the tree will be ternary. In other words: each char in the timestamp string can only be "0", "1", or "2". So...
I am also having this issue... +1 for merging this patch.
I believe the way to track something like this from a browser is through the RUM client library (see [docs](https://docs.datadoghq.com/real_user_monitoring/guide/send-rum-custom-actions/?tab=npm)). So maybe something like this, for example: ```javascript import {...
Correct, I was thinking dynamically at each request.
Ah yeah, didn't think of the limitations of passing custom implementations across to the worker...really good point. What do you think about allowing someone to pass in their own worker...