Add `Future.resolved / rejected / completed` as shortcuts for `Future.now`

[natsukagami]

Might also be thinking about naming here:

• We can have Future.resolved(T), Future.rejected(Exception) and Future.completed == Future.now to be consistent with Future.withResolver
• We can have Future.success(T) and Future.failure(Exception) to be fully similar to Future.now(Success(T)) and Future.now(Failure(Exception)).

[He-Pin]

Cool, But I have a question,it will cause some inconvenient when user use gear's Future and the current Future in Scala's stdlib? What's the plan for this？

[natsukagami]

Cool, But I have a question,it will cause some inconvenient when user use gear's Future and the current Future in Scala's stdlib? What's the plan for this？

@He-Pin You can probably easily convert a Scala stdlib Future into a gears Future. Going the other way shouldn't be too difficult but I will have to look into it.

[m8nmueller]

I have a slight personal preference for resolved/rejected because the participle indicates grammatically that an action from the lifecycle of a Future (to complete) is already taken. Either way, it's a nice thing to have.