surprised when or how many times it prints.
@sloshy This is the main thing.
Not only that, but when and how many times it gets printed can change without your calling code changing, because implementations of combinators could change, or someone could refactor code in your project in a way that's type-safe but changes the impure evaluation structure
timeoutToin a bunch of places (running on cats.effect.IO and sometimes EitherT of IO). We've noticed a pretty big perf impact from this. With the kind of traffic we get, this results in thousands of sleep operations getting placed on the sleep scheduler. Would you expect that to have a significant performance impact? I was under the impression that java schedulers were pretty good with throughput
WithContext, the IOTimer construction can't be overridden, though I might be misreading