Vert.x future type io.vertx.core.Future should be considered as a first class citizen of codegen instead of being seen as a generated type. This open several perspectives
Future type argument can be nullable (i.e Future<@Nullable String>)
In a later Vert.x version we can define asynchronous methods with a method returning a future without a callback method
It should enable future based service proxy definitions
This change adds a new ClassKind.FUTURE corresponding to the use of io.vertx.core.Future type and this type won't be anymore a generated type.
As consequence io.vertx.core.Future and io.vertx.core.CompositeFuture will not have a corresponding generated type in generators. Such type are actually irrelevant in most cases and can even be confusing (e.g with RX)
Vert.x future type
io.vertx.core.Futureshould be considered as a first class citizen of codegen instead of being seen as a generated type. This open several perspectivesThis change adds a new
ClassKind.FUTUREcorresponding to the use ofio.vertx.core.Futuretype and this type won't be anymore a generated type.As consequence
io.vertx.core.Futureandio.vertx.core.CompositeFuturewill not have a corresponding generated type in generators. Such type are actually irrelevant in most cases and can even be confusing (e.g with RX)