> I think what the user cares about is "what is the smallest tick that > this clock result will faithfully represent?". If the number of bits > returned is larger than the clock accuracy, you want the clock accuracy. > If the number of bits returned is smaller than the clock accuracy, > you want the number of bits. > > (Yes, I'm using accuracy in a slightly different sense here...I think > we don't have the right words for this.) > > To use other words, what the users cares about are the error bars on > the returned result. Ok ok, resolution / accuracy / precision are confusing (or at least not well known concepts). So it's better to keep the name: time.perf_counter() :-) Victor
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4