Hadley Wickham

I agree that something like that is likely to be useful, but it feels a bit speculative at this point, so I'm going to close this issue. Feels like something...

I made this list for a recent workshop on testing: * Output affected by RNG — `withr::local_seed()` * Output affected by other external state — `withr::local_options()` / `withr::local_envvar()` * Graphical...

@maelle in that case (especially with `local_mocked_bindings()`), mocking feels like a clear win.

It'd feel weird for `print()` to error, but maybe that's the least worst solution? Another option is to have a specific `last_lint()` helper.

https://fosstodon.org/@gaborcsardi/110961573755872008

Technically, this is correct behaviour because 0 digits are sufficient to distinguish these two numbers (-1 and 1 are different). So I'm not sure how to adapt the general rule...

Or maybe we should always just show one more digit than absolutely necessary?

@krlmlr I think that's a different bug; tracking in #162

I forgot where, but I know we've used this pattern elsewhere (i.e. on `interrupt`, warn and return the current values). But maybe we should only do this when executing in...

We could also resolve this by switching to httr2, since that has a helpers (https://httr2.r-lib.org/reference/req_retry.html and https://httr2.r-lib.org/reference/req_throttle.html) built in.