Page MenuHomePhabricator

Remove the "timeout" parameter from "Future->resolve()"
ClosedPublic

Authored by epriestley on Feb 26 2020, 4:39 PM.
Tags
None
Referenced Files
F17676983: D21031.id50138.diff
Sun, Jul 13, 11:03 AM
F17668061: D21031.id50100.diff
Sat, Jul 12, 10:51 PM
Unknown Object (File)
Jun 5 2025, 1:08 PM
Unknown Object (File)
May 30 2025, 9:55 PM
Unknown Object (File)
May 29 2025, 7:30 AM
Unknown Object (File)
May 6 2025, 3:45 PM
Unknown Object (File)
May 6 2025, 9:52 AM
Unknown Object (File)
Apr 28 2025, 10:01 PM
Subscribers
None

Details

Summary

Ref T11968. This future-level parameter has no nontrivial callers and makes the "fate of FutureGraph" changes more difficult.

Callers that are genuinely interested in this behavior can wrap the Future in a FutureIterator and use "setUpdateInterval()" to get the same behavior.

Test Plan

Grepped for "resolve()" and "resolvex()", updated callers.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable