You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
mvicsokolova
changed the title
Remove
Turn off by default / remove JS IR transformations
Apr 28, 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.
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 animplementation
dependency for the JS backend.The text was updated successfully, but these errors were encountered: