Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMissing @Nullable annotations #2434
Closed
Milestone
Comments
|
@vietj there's a similar issue with |
|
I think a single issue to fix all missing |
tsegismont
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Building this list so that we can track any missing
@Nullableannotation until 3.6 is released[ ]
Vertx.executeBlocking[ ]
Context.executeBlocking[ ]
WorkerExecutor.executeBlocking[ ]
AsyncMap.get[ ]
AsyncMap.putIfAbsent[ ]
AsyncMap.remove[ ]
AsyncMap.replace------ Original comment
Currently, the
executeBlockingresult handler type is not annotated with@Nullable.As a result, the generated Rxified API returns a
Single<T>. But it's quite common to useFuture<Void>for a blocking task which does not need to return any result.Then if the user simply invoke
future.complete(), the program fails at runtime.As a workaround, the user can use a
Future<Object>and invokecomplete()with any non-null value.