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

Turn off by default / remove JS IR transformations #431

Open
mvicsokolova opened this issue Apr 28, 2024 · 1 comment
Open

Turn off by default / remove JS IR transformations #431

mvicsokolova opened this issue Apr 28, 2024 · 1 comment
Labels
deprecation A feature that is going to deprecated and removed in future releases question

Comments

@mvicsokolova
Copy link
Collaborator

mvicsokolova commented Apr 28, 2024

It should be investigated if JS IR transformations make any performance profit on the JS backend.
If not, it's worth considering to temporarily remove support for the JS IR backend in the compiler plugin and keep kotlinx-atomicfu as an implementation dependency for the JS backend.

@mvicsokolova mvicsokolova changed the title Remove Turn off by default / remove JS IR transformations Apr 28, 2024
@mvicsokolova mvicsokolova added deprecation A feature that is going to deprecated and removed in future releases question labels Apr 28, 2024
@lppedd
Copy link

lppedd commented Apr 29, 2024

Other than performance, we should also consider bundle size.
Kotlin's stdlib already adds quite a bit to the total size, so if libraries can shave off some KBs, it's always nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deprecation A feature that is going to deprecated and removed in future releases question
Projects
None yet
Development

No branches or pull requests

2 participants