Conversation
pkozlowski-opensource
left a comment
There was a problem hiding this comment.
Thnx for the PR. While we could change to the slice usage I feel like most of the added comments just repeat what is written in the code and add to the noise instead of helping.
becc66e to
551db8a
Compare
|
@pkozlowski-opensource removed comments. |
551db8a to
832b85e
Compare
|
@alan-agius4 I removed |
832b85e to
f70b370
Compare
f70b370 to
a83c263
Compare
a83c263 to
f6bc3aa
Compare
In this commit, we improve branching in the `stringify` function, which is widely used by the framework, and add additional comments for clarification. Benchmark results of the old and new implementations (using `slice` makes it slightly faster) are as follows: ``` stringify (old version) x 117,945,419 ops/sec ±5.25% (55 runs sampled) stringify (new version) x 136,692,820 ops/sec ±4.82% (56 runs sampled) ```
f6bc3aa to
3d496a2
Compare
In this commit, we improve branching in the `stringify` function, which is widely used by the framework, and add additional comments for clarification. Benchmark results of the old and new implementations (using `slice` makes it slightly faster) are as follows: ``` stringify (old version) x 117,945,419 ops/sec ±5.25% (55 runs sampled) stringify (new version) x 136,692,820 ops/sec ±4.82% (56 runs sampled) ``` PR Close #59745
|
This PR was merged into the repository by commit cf3a507. The changes were merged into the following branches: main, 19.1.x |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
In this commit, we improve branching in the
stringifyfunction, which is widely used by the framework, and add additional comments for clarification. Benchmark results of the old and new implementations (usingslicemakes it slightly faster) are as follows: