Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vertx Sync support with ea-async or other frameworks #3187

Open
Alffrredo opened this issue Nov 9, 2019 · 2 comments
Open

Vertx Sync support with ea-async or other frameworks #3187

Alffrredo opened this issue Nov 9, 2019 · 2 comments

Comments

@Alffrredo
Copy link

Alffrredo commented Nov 9, 2019

I have used vertx Sync + Quasar and that is an awesome mix. but there are cases that implementing with quasar is hard obviously its java agent and transformation.
I think this can be a good feature to implement it with a simpler case like ea-async or other library for the same job.
I dont know is Vertx.Sync possible support to make a native image with GraalVM also or not.

@vietj
Copy link
Member

vietj commented Nov 9, 2019

I believe currently it does not work with native images because of how bytecode is generated, that being said you can contribute to vertx-sync if you want to improve it

@doctorpangloss
Copy link

I've posted the GraalVM ticket for Quasar here - oracle/graal#2546 - you're welcome to raise attention to the issue. I am also a vertx-sync user. Unfortunately based on the minimal repro I made, there will need to be more changed about how Quasar is implemented to work with Graal.

ea-async has clunkier "function coloring" i.e. everything must be CompletableFuture<> in the stack of an await call, compared to Quasar where it is just @Suspendable. This would mean that creating a runOnContext argument would be harder than it is for Quasar.

Anyway if you want something less clunky with Quasar take a look at my ticket here - puniverse/quasar#320 - to do AOT instrumentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants