benchmarks, util: use various types of values in util.inspect bench
Because the current util.inspect
benchmark only checks the performace for string formatting, we won't notice the regression for the case when util.inspect
receives non-string values.
This PR adds various types of values to the test fixture to avoid unnoticed regression in the future.
Checklist
-
make -j4 test
(UNIX), orvcbuild test
(Windows) passes -
tests and/or benchmarks are included -
commit message follows commit guidelines
Affected core subsystem(s)
util