Skip to content

use: scala-js-macrotask-executor as ExecutionContext#414

Merged
fwbrasil merged 1 commit intogetkyo:mainfrom
hearnadam:scala-js-executor
May 25, 2024
Merged

use: scala-js-macrotask-executor as ExecutionContext#414
fwbrasil merged 1 commit intogetkyo:mainfrom
hearnadam:scala-js-executor

Conversation

@hearnadam
Copy link
Copy Markdown
Collaborator

@hearnadam hearnadam commented May 25, 2024

/claim #302
/resolves #302

re: your comment @fwbrasil

I think the artifacts were not published for non-js targets after 1.1.0. If we add this only under JS settings, all is well.

Regarding build time, I think that was a bug potentially having to do with adding the dependency for all targets. For a full clean + build of core, the build time is now 28s on my machine.

Screenshot 2024-05-24 at 7 48 22 PM

I also went ahead and updated this as the executor under kyoTest. Do you think we need a direct dependency under kyo-core? I think transitive should be okay...

@fwbrasil
Copy link
Copy Markdown
Collaborator

Thanks! 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Kyo-Scheduler: scala-js-macrotask-executor as ExecutionContext on JS platform

2 participants