Timeline for Timer convenience class to time code execution for user output
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 2, 2021 at 15:24 | comment | added | riskypenguin | I see your point, thanks again for the comprehensive review! | |
| Apr 2, 2021 at 15:13 | vote | accept | riskypenguin | ||
| Apr 2, 2021 at 15:00 | comment | added | Peilonrayz♦ |
@riskypenguin By "the user" I mean "anyone who uses Timer" not "anyone who uses your library". I can understand the desire for convenience. But many times what you think is convenient at the start of the project is an inconvenience by the end of the project.
|
|
| Apr 2, 2021 at 14:57 | history | edited | Peilonrayz♦ | CC BY-SA 4.0 |
Change bad wording to something better
|
| Apr 2, 2021 at 14:46 | comment | added | riskypenguin |
Thank you for your perspective, this is really helpful (a lot of improvements I hadn't considered yet)! I should've specified, that the timer will not be used directly by the user, only the print-outs by get_timer are seen by the user. That's why I included as much convenience for myself as possible. Considering that, would you still advise against the existence of convenience methods for printing and restarting? Something like print_elapsed_and_restart?
|
|
| Apr 2, 2021 at 13:58 | history | answered | Peilonrayz♦ | CC BY-SA 4.0 |