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
As I test on many different systems ranging from 240 MHz to 4.2 GHz, using a count isn't quite useful, so I generally op for the negative value in perl5 which makes it CPU seconds
my %results = timethese(-1.5, { ... });
Type check failed in binding $count; expected 'Int' but got 'Rat'
in sub timethese at lib/Benchmark.pm6:21
The text was updated successfully, but these errors were encountered:
Sure .... however, the Perl 5 version of Benchmark relies on the "times" function to calculate CPU seconds which currently does not have an analog in Rakudo that I know about. I'll see what I can do about it.
Actually, Telemetry is so much more than that. If we want to support the basic P5 functionality, then we should have enough with nqp::getrusage. We probably want to expose that more easily than Telemetry does.
As I test on many different systems ranging from 240 MHz to 4.2 GHz, using a count isn't quite useful, so I generally op for the negative value in perl5 which makes it CPU seconds
my %results = timethese(-1.5, { ... });
Type check failed in binding $count; expected 'Int' but got 'Rat'
in sub timethese at lib/Benchmark.pm6:21
The text was updated successfully, but these errors were encountered: