-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Service Arch 2022-05-30
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
So the behavior is more clear and it's obvious that the Future class isn't the "default' or "best" of the Future types (as opposed to SemiFuture or ExecutorFuture).