@ltratt Any time I want that, it's because I want to run a thing with reference to some calendar. For example, do this at 4pm, or do this every third Sunday in a month. And that's really hard to do right. Monotonic clock for timeouts works well though. I'm going to wait for this service to respond for two seconds and, if it doesn't, I might spawn a new process to create it, for example, would be broken horribly if every suspend/resume triggered the timeout in every waiter.
What is your use case for wanting X seconds of wall-clock (but not real wall clock) time?
=> More informations about this toot | View the thread | More toots from david_chisnall@infosec.exchange
=> View ltratt@mastodon.social profile
text/gemini
This content has been proxied by September (3851b).