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
Sometimes there' some groups of classes that share a common setup on their prototypes, so it's more reasonable to use some mixins to apply those methods. Prior to static block, the application of those mixins would have been in separate statements after the classes. But regardless where it is, those calls would mark the class as sideeffectful.
I was hoping with static block enabled this would allow us to treat static block as something "internal" to a class and won't affect the sideeffect analysis of it.
classO1{static{mixinA(O1)mixinB(O1)}}
The text was updated successfully, but these errors were encountered:
Version
Current latest
Complete CLI command or
minify()
options usedN/A
terser
inputterser
output or errorExpected result
Visual:
Context
Sometimes there' some groups of classes that share a common setup on their prototypes, so it's more reasonable to use some mixins to apply those methods. Prior to static block, the application of those mixins would have been in separate statements after the classes. But regardless where it is, those calls would mark the class as sideeffectful.
I was hoping with static block enabled this would allow us to treat static block as something "internal" to a class and won't affect the sideeffect analysis of it.
The text was updated successfully, but these errors were encountered: