Page MenuHomePhabricator

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

Authored by epriestley on Feb 26 2020, 4:39 PM.
Tags
None
Referenced Files
F19508506: D21031.diff
Sat, Jan 10, 5:57 AM
F19469959: D21031.diff
Mon, Jan 5, 7:08 AM
F19417144: D21031.id50100.diff
Sat, Dec 27, 10:03 PM
F19083183: D21031.id50138.diff
Dec 2 2025, 12:31 PM
F19056819: D21031.id50100.diff
Nov 28 2025, 8:41 PM
F18985359: D21031.id50100.diff
Nov 17 2025, 12:59 PM
F18790654: D21031.id.diff
Oct 15 2025, 4:21 PM
F18783736: D21031.id50138.diff
Oct 13 2025, 9:11 AM
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